Enterprise Client Community

Hi!

Just a idea:
It could be a good thing for CaptainCasa to make it available via a maven repository.
I would expect the following benefits:
- Lower entry barrier to put CC into the own (maven) project
- Easy version updates
- Elimination of duplicated jar files
- ...?

Questions:
- Does it work with the Enterprise Client?
- Does the CC software architecture fits into the needs for maven...
- How much work it is to maintain a maven repository...

But it could be worth to think about? What do you think?

Kind regards,
Daniel

... Would also be great for ivy users...

Tobias

Hi,
...yes, we have to do something here. Currently we are just updating ourselves on Maven, so please give us a bit of time to come up with a solution (or: proposal for solution).
Regards, Björn

any news here?

...to be honest: No.

The issue "Maven" completely moved out of the focus of interest, after it popped up begin of last year.

Regards, Björn

we are just migrating everything to maven.

the weekly releases, which we always looked forward to aren't that much fun anymore. But a cc-maven repository whould cheer us up again.

to be serious, we would realy be interested in such a repository.

me/we too

To make this topic will not be forgotten: a Maven-Repository would be fine.

...please check: http://captaincasademo.com/mavenrepository/ ;-)

Regards, Björn

Hi,

Im just askin if your captain casa maven repository are up to date? Because as I am following your Setting up a Maven Project documentation. I found out that some of the jar files have new versions. Would it be okay to use the latest versions? (I mean changing what the documentation says). Thanks

Help would much be appreciated!

Hi,

the Maven repository is up to date. The current version is 20170712. - Please replace the version number that is listed in the docu by 20170712.

In the forum the official versions are published in:

http://www.captaincasademo.com/forum/forums/show/3.page

Example: in the docu there is:

Code:

 <dependency>
 <groupId>org.eclnt</groupId>
 <artifactId>eclntjsfserver</artifactId>
 <version>20161031</version>
 </dependency>

So replace 20161031 by 20170712. And please pay attention: there are (currently) two places in the Maven pom.xml which you have to replace - the version is also liste in the artifactitem within the plugin section.

Hope this helps!

Regards, Björn

Thanks for that. This is great!

How can I update my captain casa toolset? My version is the latest but the toolset is 20170703.

I have an error on my toolset editor. I am using Captain Casa with Maven and I followed your documentation too. I understand it all but I have an error

"HTTP Status 404 - /MyPOS/MainWindow.risc

type Status report

message /MyPOS/MainWindow.risc

description The requested resource is not available.

Apache Tomcat/8.0.36".

What I am missing? Help would be much appreciated.

Hi,

please check: after doing a "reload" in the Layout Editor there should be a copying of project files into the tomcat/webapps/MyPos directory. Please take a look into the .ccproject file within your project and check directories.

Maybe you could attach the file to this post?

Regards, Björn

PS: if this is your first project with CaptainCasa: we recommend to get to know development with CaptainCasa with a normal project setup (following the tutorials) and then switch to Maven afterwards.