Hi Francesco,
Ok, I now found out that it was not JUST the archetypeCatalog parameter that 
caused the problem but ALSO, the response to the "version" when the mvn was run 
to generate the archetype HAS TO BE:
1.0-SNAPSHOT
i.e., you either have to just press ENTER or enter:
1.0-SNAPSHOT
We *WERE* entering:
2.1.5
but when we enter "2.1.5", the syncope.war doesn't contain the cocoonXXXX JAR 
files (and maybe missing others also).


NOW, I am STILL a little confused about that last thing above (the "version"), 
because from your earlier response (below), it SOUNDED like you were saying 
that we could use anything that was DIFFERENT from "Syncope's coordinates"?

I interpreted that what you meant was that since the mvn was prompting with 
"1.0-SNAPSHOT", we had to enter something that was DIFFERENT from 
"1.0-SNAPSHOT"?
BUT it seems like we HAVE TO ENTER EXACTLY WHAT IS presented by mvn, at least 
for the "version", because if we enter something different, like "2.1.5", then 
Maven isn't pulling the cocoon dependencies, at least.
I am asking because even though I have it working now, if the Syncope version 
changes in the future, that will probably mean we need to enter something 
different (for at least) "version", so I want to understand how we figure out 
what we should enter in response.

Thanks,Jim


    On Monday, October 28, 2019, 5:05:22 PM UTC, [email protected] 
<[email protected]> wrote:  
 
  Hi,
I think that I've found the problem!!!
>From the dependency output, I noticed that there was output showing that it 
>was using a repo that was different than the one we had on the command line.
So I was looking at this page:
Maven Archetype Plugin – archetype:generate

| 
| 
|  | 
Maven Archetype Plugin – archetype:generate


 |

 |

 |




and noticed that the maven plugin doesn't have an "archetypeRepository" 
parameter!!!
Instead, it has an "archetypeCatalog" parameter!!!
So, I re-ran the build, using "archetypeCatalog=remote", and the WARs that I 
got ran FINE!

I want to point out that this page:
Apache Syncope 2.1.5 - Getting Started

| 
| 
| 
|  |  |

 |

 |
| 
|  | 
Apache Syncope 2.1.5 - Getting Started

Several ways to get started with Apache Syncope
 |

 |

 |




has:
$ mvn archetype:generate \
    -DarchetypeGroupId=org.apache.syncope \
    -DarchetypeArtifactId=syncope-archetype \
    -DarchetypeRepository=http://repo1.maven.org/maven2 \
    -DarchetypeVersion=2.1.5
i.e., that "mvn" command in the Syncope documentation page above is incorrect!!!
So if you concur CAN YOU PLEASE correct that?  I cannot tell you the number of 
hours/days that have been spent on this :(...

My guess is that since the plugin does not have such an "archetypeRepository" 
parameter, that it was defaulting to some unexpected repo, and then was getting 
the dependency errors.
Anyway, I have now gone back to one of my previous machines, and re-ran the 
build using "archetypeCatalog=remote" and it looks like it worked.
I am now going to try the whole thing again, on a new machine, but using Maven 
3.6.2 and hopefully that will work also.
Later,Jim




    On Monday, October 28, 2019, 3:47:19 PM UTC, Francesco Chicchiriccò 
<[email protected]> wrote:  
 
  On 28/10/19 16:43, [email protected] wrote:
  
 
 Hi, 
  Can you clarify what you mean by "provide the Maven coordinates of *your* 
project".  Specifically, what you mean by "coordinates".  Maven coordinates are 
groupId, artifactId and version.
 
  Also, what do you mean by "any values that is not CLASHING with Syncope own 
coordinates"? Are you saying that we can use any values for the responses, as 
long as they are NOT THE SAME as the defaults?  
 
I am saying you can use whatever values; only, you should take care that the 
resulting triple (groupId, artifactId, version) is not already in use by 
another Maven project.
 
If you have been using Syncope's coordinates when generating your project, you 
are doing it wrong.
 
I would suggest to get some confidence with Maven, starting with archetypes:
https://maven.apache.org/guides/introduction/introduction-to-archetypes.html
 
Regards.
 
 
      On Monday, October 28, 2019, 3:35:24 PM UTC, Francesco Chicchiriccò 
<[email protected]> wrote:  
  
     On 28/10/19 16:31, [email protected] wrote:
  
  Francesco, 
  I noticed from the paste that your provided, that it is showing " 
1.0-SNAPSHOT " 
  but when I ran the dependency try, my output was showing "2.1.5", e.g., per 
the txt file I attached earlier: 
  
  Mine: Building Apache Syncope sample project - Core 2.1.5 
   Yours: Building Apache Syncope sample project - Core 1.0-SNAPSHOT 
   ?? 
  When we run the mvn to generate the archetype we use: 
     /apps/apache-maven-3.0.5/bin/mvn archetype:generate \     
-DarchetypeGroupId=org.apache.syncope \     
-DarchetypeArtifactId=syncope-archetype \     
-DarchetypeRepository=http://repo1.maven.org/maven2 \     
-DarchetypeVersion=2.1.5   
    and for the "Define value for property 'version' 1.0-SNAPSHOT: " prompt, we 
are responding with "2.1.5" rather than just pressing ENTER. 
  Should be just pressing ENTER for that prompt? 
  Could that be the problem for us?    
 

 
 
As explained in the Getting Started guide, you need to provide the Maven 
coordinates of *your* project, not Syncope's, hence:
 
* groupId: my.company
 
* artifactId: idm
 
* version 1.0.0-SNAPSHOT
 
or any values that is not clashing with Syncope own coordinates, e.g.
 
* org.apache.syncope
 
* syncope
 
* 2.1.5
 
HTH
 Regards.
 
 -- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
      
 

 
 -- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
     

Reply via email to