DSpace

Hi,

   to reproduce the error, just download dspace-1.6.2-src-release.<any> and 
run "mvn package".

   Yes, I work with DSpace 1.6.2 for a long time, using a bunch of local 
modifications, so my first guess was I had spoiled something by accident. 
So I tried to download completely clean sources and got the same error. 
OK, I probably spoiled maven local repository (.m2/), so my colleague - 
who has never worked with DSpace (but uses maven for different projects) - 
tried to install it on his computer and the result was the same... (I 
tried to remove ~/.m2/ directory and nothing similar is in my HOME and I 
have never worked with maven as root).

   What is suprising me is that what worked last week now doesn't work and 
I didn't touch it during last weekend :-(.

   It is really weird - full log with stacktrace (mvn -e package) is 
attached (error messages at line 407). I hope it will make sense to you or 
anybody...

   Regards

   Vlastik


On Tue, 23 Oct 2012, Tim Donohue wrote:

> Hi Vlastik,
>
> The Maven central repositories for 1.6.2 have not changed (in fact, it's 
> actually impossible to modify a Maven release once it is made public). So, 
> that's not the cause here.
>
> Could you explain where you downloaded that 1.6.2 release from?  Is your copy 
> downloaded from Sourceforge? Is it accessed from GitHub?  Have you modified 
> it in any way, or is it an out-of-the-box release?
>
> Just trying to narrow down what the issues could be.  There's definitely 
> something odd going on, but it shouldn't have to do with the Maven central 
> repository. It's much more likely that something is wrong or misconfigured in 
> the 1.6.2 release you've downloaded.
>
> Finally, did Maven provide any more details to that error message?  Did it 
> say which two projects had the same identifier, or what that identifier was?
>
> - Tim
>
> On 10/23/2012 2:35 AM, Vlastimil Krejcir wrote:
>>     Hi all,
>>
>>     has anyone else encountered troubles with 'mvn package' on older DSpace
>> 1.6.2? Something has changed because I get
>> 
>> [ERROR] Two or more projects in the reactor have the same identifier, 
>> please
>> make sure that <groupId>:<artifactId>:<version> is unique for each project: 
>> ...
>> 
>> on pom.xml files. Last week mvn package works well...
>> 
>> I can't say I'm maven expert but I guess maven repositories for 1.6.2 has
>> changed.
>> 
>> Regards
>> 
>> Vlastik
>>
>> 
>> ----------------------------------------------------------------------------
>> Vlastimil Krejčíř
>> Library and Information Centre, Institute of Computer Science
>> Masaryk University, Brno, Czech Republic
>> Email: krejcir (at) ics (dot) muni (dot) cz
>> Phone: +420 549 49 3872
>> ICQ: 163963217
>> Jabber: krejvl@...
>> 
>> ----------------------------------------------------------------------------
>>
>> 
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>> _______________________________________________
>> DSpace-tech mailing list
>> DSpace-tech@...
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>> 
>

... and I have to add thata for 1.8.2 "mvn package" works...

   Vlastik

On Tue, 23 Oct 2012, Tim Donohue wrote:

> Hi Vlastik,
>
> The Maven central repositories for 1.6.2 have not changed (in fact, it's 
> actually impossible to modify a Maven release once it is made public). So, 
> that's not the cause here.
>
> Could you explain where you downloaded that 1.6.2 release from?  Is your copy 
> downloaded from Sourceforge? Is it accessed from GitHub?  Have you modified 
> it in any way, or is it an out-of-the-box release?
>
> Just trying to narrow down what the issues could be.  There's definitely 
> something odd going on, but it shouldn't have to do with the Maven central 
> repository. It's much more likely that something is wrong or misconfigured in 
> the 1.6.2 release you've downloaded.
>
> Finally, did Maven provide any more details to that error message?  Did it 
> say which two projects had the same identifier, or what that identifier was?
>
> - Tim
>
> On 10/23/2012 2:35 AM, Vlastimil Krejcir wrote:
>>     Hi all,
>>
>>     has anyone else encountered troubles with 'mvn package' on older DSpace
>> 1.6.2? Something has changed because I get
>> 
>> [ERROR] Two or more projects in the reactor have the same identifier, 
>> please
>> make sure that <groupId>:<artifactId>:<version> is unique for each project: 
>> ...
>> 
>> on pom.xml files. Last week mvn package works well...
>> 
>> I can't say I'm maven expert but I guess maven repositories for 1.6.2 has
>> changed.
>> 
>> Regards
>> 
>> Vlastik
>>
>> 
>> ----------------------------------------------------------------------------
>> Vlastimil Krejčíř
>> Library and Information Centre, Institute of Computer Science
>> Masaryk University, Brno, Czech Republic
>> Email: krejcir (at) ics (dot) muni (dot) cz
>> Phone: +420 549 49 3872
>> ICQ: 163963217
>> Jabber: krejvl@...
>> 
>> ----------------------------------------------------------------------------
>>
>> 
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>> _______________________________________________
>> DSpace-tech mailing list
>> DSpace-tech@...
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>> 
>

Hi Vlastik,

The Maven central repositories for 1.6.2 have not changed (in fact, it's 
actually impossible to modify a Maven release once it is made public). 
So, that's not the cause here.

Could you explain where you downloaded that 1.6.2 release from?  Is your 
copy downloaded from Sourceforge? Is it accessed from GitHub?  Have you 
modified it in any way, or is it an out-of-the-box release?

Just trying to narrow down what the issues could be.  There's definitely 
something odd going on, but it shouldn't have to do with the Maven 
central repository. It's much more likely that something is wrong or 
misconfigured in the 1.6.2 release you've downloaded.

Finally, did Maven provide any more details to that error message?  Did 
it say which two projects had the same identifier, or what that 
identifier was?

- Tim

On 10/23/2012 2:35 AM, Vlastimil Krejcir wrote:
>     Hi all,
>
>     has anyone else encountered troubles with 'mvn package' on older DSpace
> 1.6.2? Something has changed because I get
>
> [ERROR] Two or more projects in the reactor have the same identifier, please
> make sure that <groupId>:<artifactId>:<version> is unique for each project: ...
>
> on pom.xml files. Last week mvn package works well...
>
> I can't say I'm maven expert but I guess maven repositories for 1.6.2 has
> changed.
>
> Regards
>
> Vlastik
>
> ----------------------------------------------------------------------------
> Vlastimil Krejčíř
> Library and Information Centre, Institute of Computer Science
> Masaryk University, Brno, Czech Republic
> Email: krejcir (at) ics (dot) muni (dot) cz
> Phone: +420 549 49 3872
> ICQ: 163963217
> Jabber: krejvl@...
> ----------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@...
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>

Ahoj Vlastík,

this is probably a problem with your particular version of Maven. Did
you happen to run a system upgrade during the last week that might
have upgraded Maven? It's easy to forget to check the release notes
for a particular version of DSpace for recommended versions of build
tools.

See a similiar problem here:

http://dspace.2283337.n4.nabble.com/DSpace-1-7-0-amp-Maven-3-0-2-DuplicateProjectException-Missing-pom-xml-properties-td3339149.html

Regards,
~~helix84

No, I did not upgrade Maven and I still use version 3.0. And it works 
for a long time... Have you tried to install DSpace 1.6.2? Does it works? 
What version of maven do you use? I am very curious if someone is able to 
install 1.6.2 without any troubles (this piece of information can help me a
lot).

   I have already googled the link you suggested, however, it doesn't 
answer my question why it stops working right now...

   Vlastik

P.S. Another person (Lucka) tried it yestarday with the same result...


On Tue, 23 Oct 2012, helix84 wrote:

> Ahoj Vlastík,
>
> this is probably a problem with your particular version of Maven. Did
> you happen to run a system upgrade during the last week that might
> have upgraded Maven? It's easy to forget to check the release notes
> for a particular version of DSpace for recommended versions of build
> tools.
>
> See a similiar problem here:
>
> http://dspace.2283337.n4.nabble.com/DSpace-1-7-0-amp-Maven-3-0-2-DuplicateProjectException-Missing-pom-xml-properties-td3339149.html
>
> Regards,
> ~~helix84
>

Hi all,

   it works now. So, I have to look like an idiot... I tried it again and 
to my surprise it works. I haven't changed anything. I'm looking at the 
working mvn and I don't understand. I'm really sorry for annoying all of 
you. This must be something bigger than me, maybe then all of us, 
something between the network and the heaven... or there are ghost in our 
office or... I wish you a nice day.

   Regards

   Vlastik


On Tue, 23 Oct 2012, helix84 wrote:

> Ahoj Vlastík,
>
> this is probably a problem with your particular version of Maven. Did
> you happen to run a system upgrade during the last week that might
> have upgraded Maven? It's easy to forget to check the release notes
> for a particular version of DSpace for recommended versions of build
> tools.
>
> See a similiar problem here:
>
> http://dspace.2283337.n4.nabble.com/DSpace-1-7-0-amp-Maven-3-0-2-DuplicateProjectException-Missing-pom-xml-properties-td3339149.html
>
> Regards,
> ~~helix84
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@...
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>