junit 4.8.1 - org.junit cannot be resolved

[ykyuen]

i try to use junit 4.8.1 in my maven project by adding the following
dependency in the pom.xml

   junit
   junit
   4.8.1
   test


when i try to write the test case, the org.junit cannot be resolved(i.e.
error at "import org.junit.Assert"). but if i change the junit version to
4.7. no problem at all.

did i do anything wrong?

Thanks.
Kit










-- 
View this message in context: 
http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28385338.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Clearcase with maven release plugin

[Anders Hammar]

> > However, it does only work on the 'main' branch.
> >
>
> What do you mean by "it only works on the 'main' branch? What are the
> limitations?
>
>
The mail you've found is old and I wrote it when I had just started to use
the release plugin with clearcase. Since then I've learned more on using
that combination as well as there has been new releases of the release
plugin as well as the scm parts.
So, it works on any branch, not just the main branch. (However, you cannot
make a branch.) As long as the view you're using is set up correctly, things
will work with the release plugin.


> > Some quick things:
> > * Create $user.home/.scm/clearcase-settings.xml containing
> > 
> >   false
> > 
> >
>
> I've created the clearcase-settings.xml file in %HOME% on my Windows
> machine. And because I found a post somewhere, where they've put it in a
> .scm directory, so I copied it there.
>
> But I keep getting the following error:
>
> [INFO] Unable to checkout from SCM
> Provider message:
> The cleartool command failed.
> Command output:
> cleartool: Error: Unrecognized command option: "-vws".
>
> I have the feeling that my settings file is ignored
> Do you have an idea how I should proceed?
>
>
Sorry, no. If the file is stored as $user.home/.scm/clearcase-settings.xml
it should be picked up. Are you sure it is in the right location (for the
right user)? Execute Maven in debug mode (-X) and possibly you could get
more info.
According to the doc, you could put the file in
$maven.home/conf/clearcase-settings.xml
as well. You could try that to get something working.
Here's the doc that's available:
http://maven.apache.org/scm/clearcase.html

/Anders

Re: I have the right version, but maven can't find it

[Anders Hammar]

Just for clearity, that should be done through the dependencyManagament
section. depMgmt impacts transitive deps as well.

/Anders

On Wed, Apr 28, 2010 at 04:08, Justin Edelson wrote:

> Perhaps it is defined in a parent pom.
>
> In any case, you can fix this easily by setting the version in your pom.
>
> Justin
>
> On Apr 27, 2010, at 8:59 PM, Grant Birchmeier 
> wrote:
>
> > I can't find where the range is specified.  My output says:
> >
> > ---
> > Path to dependency:
> >1) com.connamara.ontrade:simplespreader:jar:1.0
> >2) org.marketcetera:ors:jar:1.6.0
> > ---
> >
> > But neither pom specifies a version for log4j.  I'm not even sure why
> > it looking for 1.2.13 as opposed to something later.  I see that the
> > file you linked was last updated March 31, which probably explains why
> > this trouble just started, as we last did a build prior to that.
> >
> > I got it to build by hacking my
> > ~/.m2/repository/log4j/log4j/maven-metadata-central.xml to include
> > 1.2.13.
> >
> > This is not really an optimal solution, as every user will need to do
> > this.  Is there a better way?
> >
> > (Our software uses third-party components with their own poms.  Until
> > now, we haven't had any trouble with the Maven part.  Clearly, though,
> > I'm still kind of new to this.)
> >
> > -Grant
> >
> >
> > On Tue, Apr 27, 2010 at 7:26 PM, Justin Edelson 
> wrote:
> >> Because you're using a range, which requires better metadata than log4j
> >> has. See http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml
> >>
> >> On 4/27/10 8:21 PM, Grant Birchmeier wrote:
> >>> If anyone can help, I'd appreciate it.  This is driving me up the
> >>> wall.  I tried googling, but I couldn't find what I needed.
> >>>
> >>> When I build, I get this error:
> >>>
> >>> ---
> >>> Couldn't find a version in [1.2.15, 1.2.16] to match range
> [1.2.13,1.2.13]
> >>>   log4j:log4j:jar:null
> >>> ---
> >>>
> >>> But when I list the contents of my repo dir, I clearly have a "1.2.13"
> version:
> >>>
> >>> ---
> >>> 1143 ~/$ ls ~/.m2/repository/log4j/log4j/
> >>> 1.2.13/
> >>> 1.2.14/
> >>> 1.2.15/
> >>> maven-metadata-central.xml
> >>> [...etc...]
> >>> ---
> >>>
> >>> So if I have 1.2.13 in my repo, then why is maven only finding 1.2.14
> >>> and 1.2.15?
> >>>
> >>> Thanks to anyone who can help
> >>>
> >>> -Grant
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: users-h...@maven.apache.org
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: I have the right version, but maven can't find it

[Justin Edelson]

Perhaps it is defined in a parent pom.

In any case, you can fix this easily by setting the version in your pom.

Justin

On Apr 27, 2010, at 8:59 PM, Grant Birchmeier  wrote:

> I can't find where the range is specified.  My output says:
> 
> ---
> Path to dependency:
>1) com.connamara.ontrade:simplespreader:jar:1.0
>2) org.marketcetera:ors:jar:1.6.0
> ---
> 
> But neither pom specifies a version for log4j.  I'm not even sure why
> it looking for 1.2.13 as opposed to something later.  I see that the
> file you linked was last updated March 31, which probably explains why
> this trouble just started, as we last did a build prior to that.
> 
> I got it to build by hacking my
> ~/.m2/repository/log4j/log4j/maven-metadata-central.xml to include
> 1.2.13.
> 
> This is not really an optimal solution, as every user will need to do
> this.  Is there a better way?
> 
> (Our software uses third-party components with their own poms.  Until
> now, we haven't had any trouble with the Maven part.  Clearly, though,
> I'm still kind of new to this.)
> 
> -Grant
> 
> 
> On Tue, Apr 27, 2010 at 7:26 PM, Justin Edelson  
> wrote:
>> Because you're using a range, which requires better metadata than log4j
>> has. See http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml
>> 
>> On 4/27/10 8:21 PM, Grant Birchmeier wrote:
>>> If anyone can help, I'd appreciate it.  This is driving me up the
>>> wall.  I tried googling, but I couldn't find what I needed.
>>> 
>>> When I build, I get this error:
>>> 
>>> ---
>>> Couldn't find a version in [1.2.15, 1.2.16] to match range [1.2.13,1.2.13]
>>>   log4j:log4j:jar:null
>>> ---
>>> 
>>> But when I list the contents of my repo dir, I clearly have a "1.2.13" 
>>> version:
>>> 
>>> ---
>>> 1143 ~/$ ls ~/.m2/repository/log4j/log4j/
>>> 1.2.13/
>>> 1.2.14/
>>> 1.2.15/
>>> maven-metadata-central.xml
>>> [...etc...]
>>> ---
>>> 
>>> So if I have 1.2.13 in my repo, then why is maven only finding 1.2.14
>>> and 1.2.15?
>>> 
>>> Thanks to anyone who can help
>>> 
>>> -Grant
>>> 
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>> 
>> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: I have the right version, but maven can't find it

[Grant Birchmeier]

I can't find where the range is specified.  My output says:

---
Path to dependency:
1) com.connamara.ontrade:simplespreader:jar:1.0
2) org.marketcetera:ors:jar:1.6.0
---

But neither pom specifies a version for log4j.  I'm not even sure why
it looking for 1.2.13 as opposed to something later.  I see that the
file you linked was last updated March 31, which probably explains why
this trouble just started, as we last did a build prior to that.

I got it to build by hacking my
~/.m2/repository/log4j/log4j/maven-metadata-central.xml to include
1.2.13.

This is not really an optimal solution, as every user will need to do
this.  Is there a better way?

(Our software uses third-party components with their own poms.  Until
now, we haven't had any trouble with the Maven part.  Clearly, though,
I'm still kind of new to this.)

-Grant


On Tue, Apr 27, 2010 at 7:26 PM, Justin Edelson  wrote:
> Because you're using a range, which requires better metadata than log4j
> has. See http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml
>
> On 4/27/10 8:21 PM, Grant Birchmeier wrote:
>> If anyone can help, I'd appreciate it.  This is driving me up the
>> wall.  I tried googling, but I couldn't find what I needed.
>>
>> When I build, I get this error:
>>
>> ---
>> Couldn't find a version in [1.2.15, 1.2.16] to match range [1.2.13,1.2.13]
>>   log4j:log4j:jar:null
>> ---
>>
>> But when I list the contents of my repo dir, I clearly have a "1.2.13" 
>> version:
>>
>> ---
>> 1143 ~/$ ls ~/.m2/repository/log4j/log4j/
>> 1.2.13/
>> 1.2.14/
>> 1.2.15/
>> maven-metadata-central.xml
>> [...etc...]
>> ---
>>
>> So if I have 1.2.13 in my repo, then why is maven only finding 1.2.14
>> and 1.2.15?
>>
>> Thanks to anyone who can help
>>
>> -Grant
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: I have the right version, but maven can't find it

[Justin Edelson]

Because you're using a range, which requires better metadata than log4j
has. See http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml

On 4/27/10 8:21 PM, Grant Birchmeier wrote:
> If anyone can help, I'd appreciate it.  This is driving me up the
> wall.  I tried googling, but I couldn't find what I needed.
> 
> When I build, I get this error:
> 
> ---
> Couldn't find a version in [1.2.15, 1.2.16] to match range [1.2.13,1.2.13]
>   log4j:log4j:jar:null
> ---
> 
> But when I list the contents of my repo dir, I clearly have a "1.2.13" 
> version:
> 
> ---
> 1143 ~/$ ls ~/.m2/repository/log4j/log4j/
> 1.2.13/
> 1.2.14/
> 1.2.15/
> maven-metadata-central.xml
> [...etc...]
> ---
> 
> So if I have 1.2.13 in my repo, then why is maven only finding 1.2.14
> and 1.2.15?
> 
> Thanks to anyone who can help
> 
> -Grant
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

I have the right version, but maven can't find it

[Grant Birchmeier]

If anyone can help, I'd appreciate it.  This is driving me up the
wall.  I tried googling, but I couldn't find what I needed.

When I build, I get this error:

---
Couldn't find a version in [1.2.15, 1.2.16] to match range [1.2.13,1.2.13]
  log4j:log4j:jar:null
---

But when I list the contents of my repo dir, I clearly have a "1.2.13" version:

---
1143 ~/$ ls ~/.m2/repository/log4j/log4j/
1.2.13/
1.2.14/
1.2.15/
maven-metadata-central.xml
[...etc...]
---

So if I have 1.2.13 in my repo, then why is maven only finding 1.2.14
and 1.2.15?

Thanks to anyone who can help

-Grant

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: plugin execution inheritance

[Stephen Connolly]

remember that inheritance does not have to follow aggregation (just that
life is easier when it does)

On 27 April 2010 20:58, solo1970  wrote:

>
> Hello,
>
> We had created a POM which had the execution of 3 plugins in the
>  section and all the POMs needing this plugin execution,
> was inheriting from it.
>
> We are restructuring code and now we cannot inherit from that POM anymore
> because we don't have a common parent.  Can I import a pluginManagement
> section, just like the import in dependencies???
> Is there any other way to achieve this???
>
> I hope it's clear
>
> Sonia
> --
> View this message in context:
> http://old.nabble.com/plugin-execution-inheritance-tp28381340p28381340.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: How to add jar file into a Maven 2 environment?

[Vernon]

Thanks Yoav for your information.

I would try it out if I were in a bigger development shop.



> 2010/4/23 Vernon 
>
>>
>> Thanks Yoav.
>>
>> Based on my reading (a quick scanning), JFrog does the same thing as
>> Nexus. I will use Nexus for now.
>>
>
> Same thing just a lot better :)
> Anyway, good luck!
>
>
>>
>>
>> 
>> > This article is pretty old. You may can follow the new Artifactory
>> install
>> > instructions here:
>> > http://wiki.jfrog.org/confluence/display/RTF/Installing+Artifactory
>> > A
>> > quick
>> > 1 minute setup demo is available here:
>> > http://www.youtube.com/watch?v=2FGHwZSAqog
>> >
>> > HTH,
>> >
>> > Yoav
>> >
>> > 2010/4/22 Vernon 
>> >
>> >> I find an article on the subject:
>> >> http://www.theserverside.com/news/1364121/Setting-Up-a-Maven-Repository
>> >> .
>> >> Does the procedures described in the article good enough for our
>> need?
>> >>
>> >> 
>> >> > Thanks for the information.
>> >> >
>> >> > How long it will take me to read through the book and set up an
>> >> internal
>> >> > Maven proxy server?
>> >> >
>> >> > In a non-Maven environment, we can add those jar files in a
>> minutes.
>> >> Of
>> >> > course, the downside will be a potential version issues.
>> >> >
>> >> >
>> >> > 
>> >> >> Here's a good book on the topic:
>> >> >> http://www.sonatype.com/books/nexus-book/reference/
>> >> >>
>> >> >> 2010/4/22 Vernon :
>> >> >>> Thanks a lot for your information.
>> >> >>>
>> >> >>> Where I can find a documentation on the subject (an internal
>> Maven
>> >> >>> proxy
>> >> >>> server)? I have a look at the maven documentation under the user
>> >> center
>> >> >>> and haven't find any useful information yet.
>> >> >>>
>> >> >>>
>> >> >>> 
>> >>  Right if its not in a public Maven repository you have to add it
>> to
>> >>  yours.  Ideally you will have an internal Maven proxy server
>> such
>> >> as
>> >>  Artifactory/Nexus where you can deploy it once and all can get
>> it
>> >> from
>> >>  there.
>> >> 
>> >>  (Regarding iText 5.x the reason that's not in a public maven is
>> the
>> >>  license has changed greatly starting with this version.)
>> >> 
>> >>  -Dave
>> >> 
>> >>  2010/4/20 Vernon :
>> >> >
>> >> > We need to add PayPal Java library files into our Maven
>> >> development
>> >> > environment. PayPal doesn't make any Maven artifact ID. What is
>> a
>> >> > right
>> >> > way of adding a jar file?
>> >> >
>> >> > And one more related question: shall we add jar file by
>> ourselves
>> >> for
>> >> > a
>> >> > new version of jar file? For example, the current version of
>> iText
>> >> is
>> >> > 5.0.x and the highest version with Maven artifact ID is 2.7.x.
>> >> >
>> >> > Thanks very much in advance.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> -
>> >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> > For additional commands, e-mail: users-h...@maven.apache.org
>> >> >
>> >> >
>> >> 
>> >> 
>> -
>> >>  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >>  For additional commands, e-mail: users-h...@maven.apache.org
>> >> 
>> >> 
>> >>  
>> >>  Spam/Virus scanning by CanIt Pro
>> >> 
>> >>  For more information see
>> >>  http://www.kgbinternet.com/SpamFilter.htm
>> >> 
>> >>  To control your spam filter, log in at
>> >>  http://filter.kgbinternet.com
>> >> 
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> ��插�  http://www.pu-gong-ying.info -
>> >> ��ㄧ��绀惧�轰俊＄��绔�
>> >> >>>
>> >> >>> ��伴�婚�ㄦ�� -
>> >> >>> 瀹规�蹇��版��瑙���ヨ��涓�颁富瑕���伴�绘�烘�瓒�杩�
>> 0涓���伴�绘�＄€
>> >> >>> 绀句伴�� - 涓�浠�浜哄��浜���ㄧ�浜���€
>> >> >>> �℃� -
>> 瀵绘�炬��璇�璁虹���璐���┟�€锟芥父��╁�版�姑�€
>> >> >>> ���绫诲箍��� - 寮�璐村��娴�瑙�褰���扮�绫诲箍��
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> -
>> >> >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> >>> For additional commands, e-mail: users-h...@maven.apache.org
>> >> >>>
>> >> >>>
>> >> >>
>> >> >> -
>> >> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> >> For additional commands, e-mail: users-h...@maven.apache.org
>> >> >>
>> >> >>
>> >> >> 
>> >> >> Spam/Virus scanning by CanIt Pro
>> >> >>
>> >> >> For more information see
>> >> >> http://www.kgbinternet.com/SpamFilter.htm
>> >> >>
>> >> >> To control your spam filter, log in at
>> >> >> http://filter.kgbinternet.com
>> >> >>
>> >> >
>> >> >
>> >> >

Re: plugin execution inheritance

[Anders Hammar]

No, you cannot import a pluginManagement section. And I cannot think of any
other solution for you than to specify the same configuration for each
project (unless you can change to inherit from a common parent somewhere in
the inheritance chain).

/Anders

On Tue, Apr 27, 2010 at 21:58, solo1970 wrote:

>
> Hello,
>
> We had created a POM which had the execution of 3 plugins in the
>  section and all the POMs needing this plugin execution,
> was inheriting from it.
>
> We are restructuring code and now we cannot inherit from that POM anymore
> because we don't have a common parent.  Can I import a pluginManagement
> section, just like the import in dependencies???
> Is there any other way to achieve this???
>
> I hope it's clear
>
> Sonia
> --
> View this message in context:
> http://old.nabble.com/plugin-execution-inheritance-tp28381340p28381340.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

plugin execution inheritance

[solo1970]

Hello,

We had created a POM which had the execution of 3 plugins in the
 section and all the POMs needing this plugin execution,
was inheriting from it.

We are restructuring code and now we cannot inherit from that POM anymore
because we don't have a common parent.  Can I import a pluginManagement
section, just like the import in dependencies???
Is there any other way to achieve this???

I hope it's clear

Sonia
-- 
View this message in context: 
http://old.nabble.com/plugin-execution-inheritance-tp28381340p28381340.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-dependency-plugin: Question about copy-dependencies goal

[Brian Fox]

When you compile in eclipse using m2e it's not executing the lifecycle. How
are you executing the build, exactly?

On Mon, Apr 26, 2010 at 10:23 AM, Luciano Mantuaneli <
luciano.mantuan...@cpmbraxis.com> wrote:

>  Greetings.
>
>
>
> I have a very specific need in a java project in Eclipse: The jars which
> the project depends on must be copied to an external folder.
>
>
>
> The *maven-dependency-plugin* and its *copy-*dependencies goal come to
> mind immediately.
>
>
>
> As a test, I wrote the following pom.xml:
>
>
>
> -
>
> 
>
> ...
>
> 
>
> ...
>
> 
>
>...
>
>
>
>
> org.apache.maven.plugins
>
>
> maven-dependency-plugin
>
>
>
>
>
>
> copy-dependencies
>
>
> process-resources
>
>
> 
>
>
> copy-dependencies
>
>
> 
>
>
> 
>
>
> ${my.external.location}/alterloc
>
>
> servlet-api
>
>
> 
>
>
>
>
>
>
>
> 
>
> 
>
> 
>
> -
>
>
>
> However, the above pom shows some bogus behavior, depending on the user
> action:
>
> 1)Right-clicking the project and selecting “Maven >
> Update Project Configuration”: The folder “alterloc” is created in
> “my.external.location”, and the jars, but servlet-api, are copied to it -
> Just as expected.
>
> 2)Compiling the project: The folder “dependency” is
> created in “project.build.directory”, and the jars, including servlet-api,
> are copied to it – Not expected, once the configurations seems to be ignored
>
>
>
> I already tried to change the phase to “compile”, to “process-classes”, but
> in that case it’s even worst: The dependencies wasn’t copied at all.
>
>
>
> What am I doing wrong?
>
>
>
> Thanks in advance
>
>
>
>
>
> *Luciano Mantuaneli ** *
>
>
>
> TI Melhorias - Suporte a Canais
>
>
>
> *CPM Braxis*
>
> Cel: 55 11 8399 0319
>
> Tel: 55 11 4196 4622
>
> www.cpm.com.br
>
> www.cpminternational.com
>
> www.braxis.com.br
>
>
>

Re: XML parsing error when trying to read archetype-catalog.xml

[Juven Xu]

the archetype catalog of central is fixed

On Tue, Apr 6, 2010 at 8:27 AM, Farid Derradji <
farid.derra...@itwm.fraunhofer.de> wrote:

> MY SYSTEM CONFIGURATION
>
> Operating System:   SuSE Linux 11.1
> Java Version:   JDK 1.6.0_19
>
>
>
> HOW I PRODUCED THE ERROR
>
> I wanted to create a project by typing:
>
>   mvn archetype:generate -DarchetypeCatalog=remote
>
>
> Since mvn answered that no archetype was defined, I repeated the command
> with the option -e to turn on error stack trace:
>
>   mvn -e archetype:generate -DarchetypeCatalog=remote
>
>
> Neither any archetypes were found nor any error messages were returned.
>
>
> Now I started a browser session with Firefox 3.0.13 and navigated to the
> following URL:
>
>   http://repo1.maven.org/maven2/archetype-catalog.xml
>
> But instead of displaying any contents my browser returned th following
> error message:
>
> XML Parsing Error: syntax error
> Location: http://repo1.maven.org/maven2/archetype-catalog.xml
> Line Number 1, Column 1:
>
> ArchetypeContentGenerator
> ^
>
>
> How can I solve that problem?
>
>
> Regards
> Farid
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
- juven

RE: Different behavior of Maven 2 and 3 on Flat Projekt Layout

[subir.sasikumar]

You need to add a  for parent elements. Its mandatory in
Maven 3.
Add those and your builds should work.

And you can always see other issues about compatibility by googling.

Subir

-Original Message-
From: Robert Einsle [mailto:rob...@einsle.de]
Sent: Tuesday, April 27, 2010 12:59 PM
To: Maven Users List
Subject: Different behavior of Maven 2 and 3 on Flat Projekt Layout

Hy List,

lets assume i have 3 Projects:

xx.yy.app.parent
xx.yy.app.module1
xx.yy.app.module2

.parent is Parent of both modules

--- cut ---

xx.yy.app.parent
xx.yy.app
1.0.0-SNAPSHOT

4.0.0
xx.yy.app
xx.yy.app.module1
1.0.0-SNAPSHOT
Module 1
--- cut ---

, in .parent the both modules are linked with:

--- cut ---

../xx.yy.app.module1
../xx.yy.app.module2

--- cut ---

Now i start "clean package" on Eclipse, my output is:

--- cut ---
[INFO] Scanning for projects...
[ERROR] The build could not read 2 projects -> [Help 1]
[ERROR]   The project xx.yy.app:xx.yy.app.module1:1.0.0-SNAPSHOT
(D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module1\pom.xml) has 1
error
[ERROR] Non-resolvable parent POM
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT for
xx.yy.app:xx.yy.app.module1:1.0.0-SNAPSHOT: Failed to resolve POM for
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT due to Missing:
--
1) xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT
--
1 required artifact is missing.

for artifact:
   xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT

from the specified remote repositories:
   central (http://repo1.maven.org/maven2, releases=true,
snapshots=false)
 -> [Help 2]
[ERROR]   The project xx.yy.app:xx.yy.app.module2:1.0.0-SNAPSHOT
(D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module2\pom.xml) has 1
error
[ERROR] Non-resolvable parent POM
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT for
xx.yy.app:xx.yy.app.module2:1.0.0-SNAPSHOT: Failed to resolve POM for
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT due to Missing:
--
1) xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT
--
1 required artifact is missing.

for artifact:
   xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT

from the specified remote repositories:
   central (http://repo1.maven.org/maven2, releases=true,
snapshots=false)
 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingExceptio
n
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelExcept
ion
--- cut ---

when i run this on Maven 2.2.1

--- cut ---
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Application Parent
[INFO]   Module 1
[INFO]   Module 2
[INFO]

[INFO] Building Application Parent
[INFO]task-segment: [clean, package]
[INFO]

[INFO] [clean:clean {execution: default-clean}] [INFO]
[site:attach-descriptor {execution: default-attach-descriptor}] [INFO]

[INFO] Building Module 1
[INFO]task-segment: [clean, package]
[INFO]

[INFO] [clean:clean {execution: default-clean}] [INFO] Deleting
directory D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module1\target
[INFO] [resources:resources {execution: default-resources}] [WARNING]
Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 0 resource
[INFO] [compiler:compile {execution: default-compile}] [INFO] Nothing to
compile - all classes are up to date [INFO] [resources:testResources
{execution: default-testResources}] [WARNING] Using platform encoding
(Cp1252 actually) to copy filtered resources, i.e. build is platform
dependent!
[INFO] skip non existing resourceDirectory
D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module1\src\test\resources
[INFO] [compiler:testCompile {execution: default-testCompile}] [INFO] No
sources to compile [INFO] [surefire:test {execution: default-test}]
[INFO] No tests to run.
[INFO] [jar:jar {execution: default-jar}] [INFO] Building jar:
D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module1\target\xx.yy.app.mod
ule1-1.0.0-SNAPSHOT.jar
[INFO]

[INFO] Building Module 2
[INFO]task-segment: [clean, package]
[INFO]

[INFO] [clean:clean {execution: default-clean}] [INFO] Deleting
directory D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module2\target
[INFO] [resources:resources {execution: default-resources}] [WARNING]
Using platform encoding (Cp1252 actually) to copy filtered resou

Re: Different behavior of Maven 2 and 3 on Flat Projekt Layout

[Thomas Scheffler]

Am 27.04.2010 09:28, schrieb Robert Einsle:

Hy List,

lets assume i have 3 Projects:

xx.yy.app.parent
xx.yy.app.module1
xx.yy.app.module2

.parent is Parent of both modules


Hi,

even though maven 2 supports it - kind of, I really suggest to have any 
aggregation and parent definition in the parent directory. If you one 
day have to use the release-plugin you will have less pain with this 
solution.


The real problem is eclipse not supporting multi-module project. You 
have to create a project for every module. You can just create a 
"Generic Project" give it the name of the module, e.g. 
"xx.yy.app.module1" and do NOT use the "default Location" but point 
directly to the module directory.


After long period of try and error this was the solution that worked 
best for eclipse and maven (including plugins).


Regards,

Thomas

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Release plugin & git repo with multiple projects

[Nicola Musatti]

I believe there's a very similar problem with Subversion too, when you 
have a repository for each module which are linked to the aggregator 
project by means of svn:externals. This is an approach which, as far as 
I can tell, is not supported by the release plugin.


Cheers,
Nicola Musatti

Justin Edelson wrote:

OK. Then we're on the same page...

On 4/26/10 11:32 AM, Kathryn Huxtable wrote:
   

Perhaps I wasn't clear. I don't support multiple projects in one repository. 
Definitely not. I was trying to criticize the svn-centric thinking, not support 
it.

I think there should be a JIRA issue to make modules work, given that they'll 
be in separate repositories.

I'm not going to file this because I have almost zero experience with nested 
projects. There have been places it would have made sense and I shied away.

But the release plugin should work with git projects that have modules and it 
should do it in the standard git manner, which is one repository containing one 
project. (Distributed, of course.)

-K

On Apr 26, 2010, at 9:06 AM, Justin Edelson wrote:

 

Kathryn-
Maybe I'm misunderstanding what you mean, but I think you have this
exactly backwards. The "svn-centric thinking" is what's inspired someone
to put multiple projects in the same repository. AFAIK, this is simply
not supported by git, i.e. there's no way to clone, branch or tag _part_
of a repository.

I am by no means a git expert, so I could be mistaken about this.

Justin



On 4/26/10 9:21 AM, Kathryn Huxtable wrote:
   

Having recently switched from svn to git for most of my projects, I have an 
opinion.

I think you should create a JIRA ticket and consider this a bug.

What we're dealing with here is a bit of svn-centric thinking during design. It 
needs to be fixed.

-K

On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote:

 

We're considering migrating from svn to git, we stumble on the
maven-release-plugin usage with git.
We think we prefer to use a single repository for many independently built
projects like :

foobar-repo.git
  |->  project-foo/
  ||->  pom.xml
  ||–>  module A/
  ||->  module B/
  |
  |->  project-bar/
   |->  pom.xml


project-bar scm url looks like :
scm:git:ssh://somehost.nowhere:/foobar-repo.git

This hints to the right repository but I can't write that the actual
project-bar is in the project-bar subdirectory.

mvn release:prepare goes well and ends succesfully.

mvn release:perform fails whenever it tries to build the project from the
tag. It effectively clone correctly the repository.
But use the root of the repository rather than going into project-bar
subdirectory whenever it tries to clean deploy the tag.

This prevent using git and multiple projects in the same directory.
Some may think we should use gitmodules but
1) the release plugin does not support it [1]
2) gitmodules is an aggregate of single repository

Should I issue a "new feature" ticket into jira project MRELEASE or SCM ?
Or should I fall back to the current convention of 1 project = 1 git
repository ??
Or maybe someone managed to do it ?

any advice appreciated.

[1] : http://jira.codehaus.org/browse/SCM-530
   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


   



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Force Maven to use my newer version of Jaxb instead of the onefrom Java 6?

[VanIngen, Erik (FIPS)]

thank you for the good answer!

-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com] 
Sent: 26 April 2010 18:32
To: Maven Users List
Subject: Re: Force Maven to use my newer version of Jaxb instead of the
onefrom Java 6?


> How can force Maven to use my newer version of Jaxb instead of the one 
> from Java 6?

This is not a Maven problem per-se. You can find ways to deal with this here:
https://jaxb.dev.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.h
tml

The easiest approach is using the endorsed directory mechanism but realize
this means you need to deploy jars to all JDKs/JREs in your environments.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Different behavior of Maven 2 and 3 on Flat Projekt Layout

[Robert Einsle]

Hy List,

lets assume i have 3 Projects:

xx.yy.app.parent
xx.yy.app.module1
xx.yy.app.module2

.parent is Parent of both modules

--- cut ---

xx.yy.app.parent
xx.yy.app
1.0.0-SNAPSHOT

4.0.0
xx.yy.app
xx.yy.app.module1
1.0.0-SNAPSHOT
Module 1
--- cut ---

, in .parent the both modules are linked with:

--- cut ---

../xx.yy.app.module1
../xx.yy.app.module2

--- cut ---

Now i start "clean package" on Eclipse, my output is:

--- cut ---
[INFO] Scanning for projects...
[ERROR] The build could not read 2 projects -> [Help 1]
[ERROR]   The project xx.yy.app:xx.yy.app.module1:1.0.0-SNAPSHOT 
(D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module1\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM 
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT for 
xx.yy.app:xx.yy.app.module1:1.0.0-SNAPSHOT: Failed to resolve POM for 
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT due to Missing:

--
1) xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT
--
1 required artifact is missing.

for artifact:
  xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
-> [Help 2]
[ERROR]   The project xx.yy.app:xx.yy.app.module2:1.0.0-SNAPSHOT 
(D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module2\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM 
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT for 
xx.yy.app:xx.yy.app.module2:1.0.0-SNAPSHOT: Failed to resolve POM for 
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT due to Missing:

--
1) xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT
--
1 required artifact is missing.

for artifact:
  xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
-> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the 
-e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

--- cut ---

when i run this on Maven 2.2.1

--- cut ---
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Application Parent
[INFO]   Module 1
[INFO]   Module 2
[INFO] 


[INFO] Building Application Parent
[INFO]task-segment: [clean, package]
[INFO] 


[INFO] [clean:clean {execution: default-clean}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] 


[INFO] Building Module 1
[INFO]task-segment: [clean, package]
[INFO] 


[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory 
D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module1\target

[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered 
resources, i.e. build is platform dependent!

[INFO] Copying 0 resource
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources {execution: default-testResources}]
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered 
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory 
D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module1\src\test\resources

[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [surefire:test {execution: default-test}]
[INFO] No tests to run.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar: 
D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module1\target\xx.yy.app.module1-1.0.0-SNAPSHOT.jar
[INFO] 


[INFO] Building Module 2
[INFO]task-segment: [clean, package]
[INFO] 


[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory 
D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module2\target

[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered 
resources, i.e. build is platform dependent!

[INFO] Copying 0 resource
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources {execution: default-testResources}]
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered 
resources, i.e. build is platform depen

Re: Dependency Management +

[Morten Kjetland]

We use a plugin called deptools to automatically fail the build if a
maven chooses a dependency that is older than the version some other
dependency requires it to be..

Have a look at it here:
http://github.com/mbknor/deptools

-Morten


On Mon, Apr 26, 2010 at 6:12 PM, Nick Stolwijk  wrote:
> To enforce that all plugins are versioned use the enforcer plugin [1]
> with the rule requirePluginVersions [2].
>
> For the dependencymanagement enforcement take a look at the Maven
> Dependency Plugin [3] with the goals analyze-only [4] and
> anaylyze-dep-mgt [5].
>
> [1] http://maven.apache.org/plugins/maven-enforcer-plugin/
> [2] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html
> [3] http://maven.apache.org/plugins/maven-dependency-plugin/
> [4] 
> http://maven.apache.org/plugins/maven-dependency-plugin/analyze-only-mojo.html
> [5] 
> http://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html
>
> Hth,
>
> Nick Stolwijk
> ~Java Developer~
>
> IPROFS BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> http://www.iprofs.nl
>
>
>
> On Mon, Apr 26, 2010 at 5:59 PM, solo1970
>  wrote:
>>
>> Hello,
>>
>> For my project, I need to identify plugins/dependencies that don't have
>> explicit versions specified (i.e. that would use the latest version)
>>
>> Also, I would need a plugin to fail my build if the aggregated modules don't
>> use the same version of inter-project dependencies. (would check for project
>> dependency inconsistency)
>>
>> Any ideas?
>>
>> Sonia
>> --
>> View this message in context: 
>> http://old.nabble.com/Dependency-Management-%2B-tp28366761p28366761.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org