date:20090127

Hi to all,

We're using maven to build all our company projects for about 6 months
and are very happy with it.
Some of our projects, mainly Eclipse RCP plugins, are also mavenized.

We know think about OSGIfing more of our projects (server side) and
track ASF projects Felix of course core but also ServiceMix Kernel.

BTW, we wonder if there is a consensus or strategy about OSGIfied
artifacts and their location in external repositories.

- Should we repackage our current projects to produce both jar and plugins ?

- How and where to store these artifacts to make sure Felix could get
it (did a Nexus repository could do the job).

- How to 'mark' artifacts to indicate the difference between strict
jar and OSIG jars (bundles). Eclipse prefix then with org.eclipse, SS
with com.springsource ?


Advices and experience are more than welcome.

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

Re: create war and jar files at same time.

2009-01-27 Thread Yves Dessertine

Okay. You can't define two packaging types (I think, not 100% sure).

But,

you can attach other plugins to the package phase. I did this.
Something like this in your plugins section. Example:

   plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-war-plugin/artifactId
   version2.1-alpha-1/version
   configuration
   !-- your war plugin conf here (see
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html ) --
   /configuration
   /plugin


Forget about adding one more submodule :)

Regards,

2009/1/27 Yves Dessertine yvesd.pub...@gmail.com:
 Okay. You can't define two packaging types (I think, not 100% sure).

 But,

 you can attach other plugins to the package phase. I did this.
 Something like this in your plugins section. Example:

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1/version
configuration
!-- your war plugin conf here (see
 http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html ) --
/configuration
/plugin


 Forget about adding one more submodule :)

 Regards,

 Yves


 2009/1/27 Minhaj minhaj...@gmail.com:
 thanks for your reply,

 but the problem is i want to create jar and war for the same module like we
 can do in ant...we can specify goals for creating jar and war separately and
 then execute by command prompt ant war or ant jar


 Tx
 Minhaj

 On Tue, Jan 27, 2009 at 2:57 PM, Yves Dessertine yvesd.pub...@gmail.com
 wrote:

 Is it an acceptable solution for you, to create one more subproject
 generating a jar. And then make the war-project depend on your jar ?

 PS : don't crosspost on dev and users (this questions has nothing to
 do with dev, don't ?)

 Yves

 2009/1/27 Minhaj minhaj...@gmail.com:
  Hi,
 
  i am working on maven;s multi module project i have three modules with
  three
  pom.xml files all of them generating war files successfully and i want
  to
  generate a jar file as well for one of the module.
 
  i am confuse that how can we define two times the packaging tag in
  same
  pom.xml file.
 
  it can be done with Profiles??
 
 
  Tx
  Minhajkk
 




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

Re: maven / osgi / repositories

2009-01-27 Thread Samuel Le Berrigaud

Hi Henri,

it seems to me that OSGi jars are not meant to be anything else that
traditional jars with extra information in their MANIFEST. I would
definitely recomment deploying them as standard jar as you would do
for any normal maven project.

One thing that could/would differentiate your OSGi jars is that if you
use the maven bundle plugin
[http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html]
then the pom deployed along side your jar will have the packaging set
to bundle. To me it seems like enough information.

Another point of reference you might consider is how the springsource
guys make OSGi-ified version of many java libraries in their bundle
repository [http://www.springsource.com/repository/]. This acts pretty
much as a simple maven repository delivering jars.

Also I know that the Felix guys have an initiative around an OSGi
Bundle Repository (OBR)
[http://felix.apache.org/site/apache-felix-osgi-bundle-repository.html].
This is meant to be a repository that is more OSGi specific. I could
help with dependency resolution -- just as maven does -- by
introspecting jars MANIFESTs.

Archiva or Nexus would most probably satisfy your needs for maven
repositories. They might become OBRs at some point when OSGi becomes
more mainstream.

Hope this helps,
SaM

On Tue, Jan 27, 2009 at 10:24 PM, Henri Gomez henri.go...@gmail.com wrote:
 Hi to all,

 We're using maven to build all our company projects for about 6 months
 and are very happy with it.
 Some of our projects, mainly Eclipse RCP plugins, are also mavenized.

 We know think about OSGIfing more of our projects (server side) and
 track ASF projects Felix of course core but also ServiceMix Kernel.

 BTW, we wonder if there is a consensus or strategy about OSGIfied
 artifacts and their location in external repositories.

 - Should we repackage our current projects to produce both jar and plugins ?

 - How and where to store these artifacts to make sure Felix could get
 it (did a Nexus repository could do the job).

 - How to 'mark' artifacts to indicate the difference between strict
 jar and OSIG jars (bundles). Eclipse prefix then with org.eclipse, SS
 with com.springsource ?


 Advices and experience are more than welcome.

 -
 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

locked out of archiva

2009-01-27 Thread Ed Young

I find myself unable to log into archiva (v 1.1.3 standalone on an ubuntu
box). I suspect the passwords all expired but not sure. I've tried the email
password reset, but it the link it sends does me no good,  because it just
allows me to try to log in again.

I did a search and it seems this has happened before to others, but I
couldn't determine the fix...

I have full root access to the machine so is there a way to tweak the config
files or something to get me back in to fix things?

Thanks,

-- 
- Ed

[M2] Repository Manager

2009-01-27 Thread Matthias Müller

Hi there, 

i'm quite new to maven. i want to setup a shared internal remote repository on 
a network drive. the users use there own local repository (~/.m2/repository) as 
a cache and for their unreleased projects. if the project need an artifact that 
is not in the internal remote repository, that artifacts need to be downloaded 
from central to that internal remote repository and then copied to the local 
one. 
what's the easiest way to accomplish that?
is that the purpose of request managers like Nexus?
what request managers do you recommend?

regards, matthias





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

Re: [M2] Repository Manager

2009-01-27 Thread Martin Höller

Hi!

On Tuesday 27 January 2009 Matthias Müller wrote:
 i'm quite new to maven. i want to setup a shared internal remote
 repository on a network drive. the users use there own local repository
 (~/.m2/repository) as a cache and for their unreleased projects. if the
 project need an artifact that is not in the internal remote repository,
 that artifacts need to be downloaded from central to that internal remote
 repository and then copied to the local one. what's the easiest way to
 accomplish that?
 is that the purpose of request managers like Nexus?
 what request managers do you recommend?

Usually these software packages are refered to as repository managers 
rather than request managers. However, Nexus, Archiva or Artifactory are 
such repository managers. A list is available on maven's homepage [0] or at 
codehaus.org [1].

You will also find some posts if you search this list's archive with nabble [2]

hth,
- martin

[0] http://maven.apache.org/repository-management.html
[1] 
http://docs.codehaus.org/display/MAVENUSER/Maven%2BRepository%2BManager%2BFeature%2BMatrix
[2] http://www.nabble.com/Maven---Users-f178.html


signature.asc
Description: This is a digitally signed message part.

Re: locked out of archiva

2009-01-27 Thread Martin Höller

Hi!

On Tuesday 27 January 2009 Ed Young wrote:
 I find myself unable to log into archiva (v 1.1.3 standalone on an ubuntu
 box). I suspect the passwords all expired but not sure. I've tried the
 email password reset, but it the link it sends does me no good,  because
 it just allows me to try to log in again.

Read this thread [0] on the archiva mailing list.

In general, questions like this are better posted to the archiva list.

hth,
- martin

[0] http://www.nabble.com/Admin-account-locked-to15318269.html#a15318434


signature.asc
Description: This is a digitally signed message part.

Re: maven / osgi / repositories

2009-01-27 Thread Holger Hoffstaette

On Tue, 27 Jan 2009 22:53:10 +1100, Samuel Le Berrigaud wrote:

 Another point of reference you might consider is how the springsource
 guys make OSGi-ified version of many java libraries in their bundle
 repository [http://www.springsource.com/repository/]. This acts pretty
 much as a simple maven repository delivering jars.

..with renamed group/artifactIds, which _completely_ destroys the entire
transitive dependency resolution.

-h



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

Re: maven / osgi / repositories

 Another point of reference you might consider is how the springsource
 guys make OSGi-ified version of many java libraries in their bundle
 repository [http://www.springsource.com/repository/]. This acts pretty
 much as a simple maven repository delivering jars.

 ..with renamed group/artifactIds, which _completely_ destroys the entire
 transitive dependency resolution.

That's one of my concern.

Different group/artifactid make a split between developpement and runtime ;(

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

Re: maven / osgi / repositories

 Hi Henri,

 it seems to me that OSGi jars are not meant to be anything else that
 traditional jars with extra information in their MANIFEST. I would
 definitely recomment deploying them as standard jar as you would do
 for any normal maven project.

Simple jar with MANIFEST, but today very few maven artifact are
OSGIfied, so so should geth OSGIfied jars elsewhere or with a
different group/artifact id ;(

 One thing that could/would differentiate your OSGi jars is that if you
 use the maven bundle plugin
 [http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html]
 then the pom deployed along side your jar will have the packaging set
 to bundle. To me it seems like enough information.

For inhouse projects, it's not a problem and we allready do that from
our RCP projects, but the problem is still here for external projects,
ie ant, jaxws...

 Another point of reference you might consider is how the springsource
 guys make OSGi-ified version of many java libraries in their bundle
 repository [http://www.springsource.com/repository/]. This acts pretty
 much as a simple maven repository delivering jars.

I see that but the group/artifact is not the same that the one used in
developpement, hard after that to get a clean trace from developpment
to runtime :(

 Also I know that the Felix guys have an initiative around an OSGi
 Bundle Repository (OBR)
 [http://felix.apache.org/site/apache-felix-osgi-bundle-repository.html].
 This is meant to be a repository that is more OSGi specific. I could
 help with dependency resolution -- just as maven does -- by
 introspecting jars MANIFESTs.

A good idea, it will be nice to get it as maven central.

And in the long term, get all 'maven' artifact converted to
osgi-bundle (very long term).

Or may by specializing maven request, ie I need ant-1.7.2 jar,
ant-1.7.2 osgi-bundle.
So we could have simple jar and bundle at the same location in maven repo.

 Archiva or Nexus would most probably satisfy your needs for maven
 repositories. They might become OBRs at some point when OSGi becomes
 more mainstream.

I think there is plan for this in Nexus.

 Hope this helps,
 SaM

Thanks for your time Sam, it was helpfull :)

 On Tue, Jan 27, 2009 at 10:24 PM, Henri Gomez henri.go...@gmail.com wrote:
 Hi to all,

 We're using maven to build all our company projects for about 6 months
 and are very happy with it.
 Some of our projects, mainly Eclipse RCP plugins, are also mavenized.

 We know think about OSGIfing more of our projects (server side) and
 track ASF projects Felix of course core but also ServiceMix Kernel.

 BTW, we wonder if there is a consensus or strategy about OSGIfied
 artifacts and their location in external repositories.

 - Should we repackage our current projects to produce both jar and plugins ?

 - How and where to store these artifacts to make sure Felix could get
 it (did a Nexus repository could do the job).

 - How to 'mark' artifacts to indicate the difference between strict
 jar and OSIG jars (bundles). Eclipse prefix then with org.eclipse, SS
 with com.springsource ?


 Advices and experience are more than welcome.

 -
 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

AW: [M2] Repository Manager

2009-01-27 Thread Matthias Müller

Hi Martin,

i installed the nexus repository manager and although it's way more than i
need, it works for my needs.
thanks, matthias

- Ursprüngliche Mail
Von: Martin Höller mar...@xss.co.at
An: Maven Users List users@maven.apache.org
Gesendet: Dienstag, den 27. Januar 2009, 13:29:46 Uhr
Betreff: Re: [M2] Repository Manager

Hi!

On Tuesday 27 January 2009 Matthias Müller wrote:
i'm quite new to maven. i want to setup a shared internal remote
repository on a network drive. the users use there own local repository
(~/.m2/repository) as a cache and for their unreleased projects. if the
project need an artifact that is not in the internal remote repository,
that artifacts need to be downloaded from central to that internal remote
repository and then copied to the local one. what's the easiest way to
accomplish that?
is that the purpose of request managers like Nexus?
what request managers do you recommend?

Usually these software packages are refered to as repository managers
rather than request managers. However, Nexus, Archiva or Artifactory are
such repository managers. A list is available on maven's homepage [0] or at
codehaus.org [1].

You will also find some posts if you search this list's archive with nabble [2]

hth,
- martin

[0] http://maven.apache.org/repository-management.html
[1]
http://docs.codehaus.org/display/MAVENUSER/Maven%2BRepository%2BManager%2BFeature%2BMatrix
[2] http://www.nabble.com/Maven---Users-f178.html

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

RE: [M2] Repository Manager

Yes, a shared repository is needed in a team and a proxy can also help speed 
things up. This is exactly the purpose of the repo managers. You can find more 
information at:
http://maven.apache.org/repository-management.html

-Original Message-
From: Matthias Müller [mailto:pym...@yahoo.de] 
Sent: Tuesday, January 27, 2009 7:20 AM
To: users@maven.apache.org
Subject: [M2] Repository Manager

Hi there, 

i'm quite new to maven. i want to setup a shared internal remote repository on 
a network drive. the users use there own local repository (~/.m2/repository) as 
a cache and for their unreleased projects. if the project need an artifact that 
is not in the internal remote repository, that artifacts need to be downloaded 
from central to that internal remote repository and then copied to the local 
one. 
what's the easiest way to accomplish that?
is that the purpose of request managers like Nexus?
what request managers do you recommend?

regards, matthias

-
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

Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

Hello,

I want to use a parent POM as a way to easily give some organisation specific 
information to the new projects in our company or the old one being mavenized.

I don't want to declare all the projects of my company as being a module of 
this parent POM. It doesn't make much sense. So the parent POM has no modules 
tag.

When using the release plugin, though, I realized it is considering the project 
having a parent POM as a module (therefore adding the module name to the SCM 
string).

So, I am wondering:
 - does having a parent POM make the current POM a module ?
 - If so, how can I implement this organisation POM stuff I need ?
 - If not, is there something wrong with the way I use the release plugin or is 
there an option to avoid the SCM string problem ?

Thanks for any insight on this matter,

Sébastien Lesaint


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

RE: [M2] Repository Manager

Matthias, if you have questions about using Nexus, there is a #nexus channel on 
irc.codehaus.org and a nexus-user list @ 
http://nexus.sonatype.org/dev/mailing-lists.html

-Original Message-
From: Matthias Müller [mailto:pym...@yahoo.de] 
Sent: Tuesday, January 27, 2009 8:21 AM
To: Maven Users List
Subject: AW: [M2] Repository Manager

Hi Martin,

i installed the nexus repository manager and although it's way more than i 
need, it works for my needs.
thanks, matthias

- Ursprüngliche Mail 
Von: Martin Höller mar...@xss.co.at
An: Maven Users List users@maven.apache.org
Gesendet: Dienstag, den 27. Januar 2009, 13:29:46 Uhr
Betreff: Re: [M2] Repository Manager

Hi!

On Tuesday 27 January 2009 Matthias Müller wrote:
 i'm quite new to maven. i want to setup a shared internal remote
 repository on a network drive. the users use there own local repository
 (~/.m2/repository) as a cache and for their unreleased projects. if the
 project need an artifact that is not in the internal remote repository,
 that artifacts need to be downloaded from central to that internal remote
 repository and then copied to the local one. what's the easiest way to
 accomplish that?
 is that the purpose of request managers like Nexus?
 what request managers do you recommend?

Usually these software packages are refered to as repository managers 
rather than request managers. However, Nexus, Archiva or Artifactory are 
such repository managers. A list is available on maven's homepage [0] or at 
codehaus.org [1].

You will also find some posts if you search this list's archive with nabble [2]

hth,
- martin

[0] http://maven.apache.org/repository-management.html
[1] 
http://docs.codehaus.org/display/MAVENUSER/Maven%2BRepository%2BManager%2BFeature%2BMatrix
[2] http://www.nabble.com/Maven---Users-f178.html

-
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: [M2] Repository Manager

2009-01-27 Thread Baptiste MATHUS

I'd be curious to know what makes you say that it's way more than you
need. Though you're using nexus, I guess your opinion might benefit to
usability concerns for all repo managers. Too complex to setup? Other?

Cheers.

2009/1/27 Matthias Müller pym...@yahoo.de

Hi Martin,

i installed the nexus repository manager and although it's way more than i
need, it works for my needs.
thanks, matthias

- Ursprüngliche Mail
Von: Martin Höller mar...@xss.co.at
An: Maven Users List users@maven.apache.org
Gesendet: Dienstag, den 27. Januar 2009, 13:29:46 Uhr
Betreff: Re: [M2] Repository Manager

Hi!

You will also find some posts if you search this list's archive with nabble
[2]

hth,
- martin

[0] http://maven.apache.org/repository-management.html
[1]
http://docs.codehaus.org/display/MAVENUSER/Maven%2BRepository%2BManager%2BFeature%2BMatrix
[2] http://www.nabble.com/Maven---Users-f178.html

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

--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

RE: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

The parent / child relationship != modules. That is a given pom can inherit 
from one parent and be aggregated as a module via another. It is true that 
usually they are the same, but for top level poms (corporate poms or team poms 
we call them) you usually would not have any modules even though everything 
inherits from it.

However, urls are generated using the inheritance tree and each artifactId is 
inserted along the way. If this isn't what you want, then it needs to be 
redefined at the top of your project. Then the modules of that project would 
correctly inherit the url.

-Original Message-
From: Lesaint Sébastien [mailto:sebastien.lesa...@ginerativ.fr] 
Sent: Tuesday, January 27, 2009 9:01 AM
To: Maven Users List
Subject: Does having a parent POM mean the current POM is a module ? (or a 
possible release plugin issue)

Hello,

I want to use a parent POM as a way to easily give some organisation specific 
information to the new projects in our company or the old one being mavenized.

I don't want to declare all the projects of my company as being a module of 
this parent POM. It doesn't make much sense. So the parent POM has no modules 
tag.

When using the release plugin, though, I realized it is considering the project 
having a parent POM as a module (therefore adding the module name to the SCM 
string).

So, I am wondering:
 - does having a parent POM make the current POM a module ?
 - If so, how can I implement this organisation POM stuff I need ?
 - If not, is there something wrong with the way I use the release plugin or is 
there an option to avoid the SCM string problem ?

Thanks for any insight on this matter,

Sébastien Lesaint


-
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: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

2009-01-27 Thread Baptiste MATHUS

We have a parent pom for the exact kind of things you speak about. But our
projects are not modules (at least not all). So no.
Your problem with scm tag might just be related to the fact you didn't set
the maven-release-plugin tagBase configuration?

See http://maven.apache.org/plugins/maven-release-plugin/usage.html for more
information.

Cheers.

2009/1/27 Lesaint Sébastien sebastien.lesa...@ginerativ.fr

 Hello,

 I want to use a parent POM as a way to easily give some organisation
 specific information to the new projects in our company or the old one being
 mavenized.

 I don't want to declare all the projects of my company as being a module of
 this parent POM. It doesn't make much sense. So the parent POM has no
 modules tag.

 When using the release plugin, though, I realized it is considering the
 project having a parent POM as a module (therefore adding the module name to
 the SCM string).

 So, I am wondering:
  - does having a parent POM make the current POM a module ?
  - If so, how can I implement this organisation POM stuff I need ?
  - If not, is there something wrong with the way I use the release plugin
 or is there an option to avoid the SCM string problem ?

 Thanks for any insight on this matter,

 Sébastien Lesaint


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




-- 
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

RE: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

Indeed, no, I didn't set the tagBase. Even though I don't understand what it is 
yet, I guess it will solve my problem.

I had seen that when reading the documentation but I though it didn't apply to 
CVS (the SCM we use).

Thanks Baptiste

Sébastien Lesaint 

-Message d'origine-
De : bmat...@gmail.com [mailto:bmat...@gmail.com] De la part de Baptiste MATHUS
Envoyé : mardi 27 janvier 2009 15:07
À : Maven Users List
Objet : Re: Does having a parent POM mean the current POM is a module ? (or a 
possible release plugin issue)

We have a parent pom for the exact kind of things you speak about. But our
projects are not modules (at least not all). So no.
Your problem with scm tag might just be related to the fact you didn't set
the maven-release-plugin tagBase configuration?

See http://maven.apache.org/plugins/maven-release-plugin/usage.html for more
information.

Cheers.

2009/1/27 Lesaint Sébastien sebastien.lesa...@ginerativ.fr

 Hello,

 I want to use a parent POM as a way to easily give some organisation
 specific information to the new projects in our company or the old one being
 mavenized.

 I don't want to declare all the projects of my company as being a module of
 this parent POM. It doesn't make much sense. So the parent POM has no
 modules tag.

 When using the release plugin, though, I realized it is considering the
 project having a parent POM as a module (therefore adding the module name to
 the SCM string).

 So, I am wondering:
  - does having a parent POM make the current POM a module ?
  - If so, how can I implement this organisation POM stuff I need ?
  - If not, is there something wrong with the way I use the release plugin
 or is there an option to avoid the SCM string problem ?

 Thanks for any insight on this matter,

 Sébastien Lesaint


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




-- 
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

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

Re: create war and jar files at same time.

2009-01-27 Thread Wendy Smoak

[Answered only on users@ list.  Please don't cross-post.]

On Tue, Jan 27, 2009 at 1:08 AM, Minhaj minhaj...@gmail.com wrote:

 i am working on maven;s multi module project i have three modules with three
 pom.xml files all of them generating war files successfully and i want to
 generate a jar file as well for one of the module.

It's better to create a separate jar module for the classes you want
to package in a jar, and add it as a dependency in your war module.

If that doesn't make sense for your project, then you can configure
the war plugin to create an 'attached' jar by configuring the war
plugin:

http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#attachClasses

-- 
Wendy

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

[ANN] Registration for ApacheCon Europe 2009 is now open!

-Original Message-
From: ApacheCon EU 2009 [mailto:curc...@apache.org] 
Sent: Tuesday, January 27, 2009 9:04 AM
To: annou...@apache.org
Subject: [ANN] Registration for ApacheCon Europe 2009 is now open!

ApacheCon EU 2009 registration is now open!
23-27 March -- Mövenpick Hotel, Amsterdam, Netherlands
http://www.eu.apachecon.com/

Registration for ApacheCon Europe 2009 is now open - act before early
bird prices expire 6 February.  Remember to book a room at the Mövenpick
and use the Registration Code: Special package attendees for the
conference registration, and get 150 Euros off your full conference
registration.

Lower Costs - Thanks to new VAT tax laws, our prices this year are 19%
lower than last year in Europe!  We've also negotiated a Mövenpick rate
  of a maximum of 155 Euros per night for attendees in our room block.

Quick Links:

http://xrl.us/aceu09sa  See the schedule
http://xrl.us/aceu09ha  Get your hotel room
http://xrl.us/aceu09ra  Register for the conference

Other important notes:

- Geeks for Geeks is a new mini-track where we can feature advanced
technical content from project committers.  And our Hackathon on Monday
and Tuesday is open to all attendees - be sure to check it off in your
registration.

- The Call for Papers for ApacheCon US 2009, held 2-6 November
2009 in Oakland, CA, is open through 28 February, so get your
submissions in now.  This ApacheCon will feature special events with
some of the ASF's original founders in celebration of the 10th
anniversary of The Apache Software Foundation.

http://www.us.apachecon.com/c/acus2009/

- Interested in sponsoring the ApacheCon conferences?  There are plenty
of sponsor packages available - please contact Delia Frees at
de...@apachecon.com for further information.

==
ApacheCon EU 2008: A week of Open Source at it's best!

Hackathon - open to all! | Geeks for Geeks | Lunchtime Sessions
In-Depth Trainings | Multi-Track Sessions | BOFs | Business Panel
Lightning Talks | Receptions | Fast Feather Track | Expo... and more!

- Shane Curcuru, on behalf of
   Noirin Shirley, Conference Lead,
   and the whole ApacheCon Europe 2009 Team
   http://www.eu.apachecon.com/  23-27 March -- Amsterdam, Netherlands

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

RE: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

Thanks for you answer, Brian.

How do I redefine at the top of my project so that the URLs are generated the 
way I want (not appending the artifactId)?

Sébastien Lesaint


-Message d'origine-
De : Brian E. Fox [mailto:bri...@reply.infinity.nu] 
Envoyé : mardi 27 janvier 2009 15:06
À : Maven Users List
Objet : RE: Does having a parent POM mean the current POM is a module ? (or a 
possible release plugin issue)

The parent / child relationship != modules. That is a given pom can inherit 
from one parent and be aggregated as a module via another. It is true that 
usually they are the same, but for top level poms (corporate poms or team poms 
we call them) you usually would not have any modules even though everything 
inherits from it.

However, urls are generated using the inheritance tree and each artifactId is 
inserted along the way. If this isn't what you want, then it needs to be 
redefined at the top of your project. Then the modules of that project would 
correctly inherit the url.

-Original Message-
From: Lesaint Sébastien [mailto:sebastien.lesa...@ginerativ.fr] 
Sent: Tuesday, January 27, 2009 9:01 AM
To: Maven Users List
Subject: Does having a parent POM mean the current POM is a module ? (or a 
possible release plugin issue)

Hello,

I want to use a parent POM as a way to easily give some organisation specific 
information to the new projects in our company or the old one being mavenized.

I don't want to declare all the projects of my company as being a module of 
this parent POM. It doesn't make much sense. So the parent POM has no modules 
tag.

When using the release plugin, though, I realized it is considering the project 
having a parent POM as a module (therefore adding the module name to the SCM 
string).

So, I am wondering:
 - does having a parent POM make the current POM a module ?
 - If so, how can I implement this organisation POM stuff I need ?
 - If not, is there something wrong with the way I use the release plugin or is 
there an option to avoid the SCM string problem ?

Thanks for any insight on this matter,

Sébastien Lesaint


-
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: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

I didn't find much explaining how the tagBase works or what it is.

Basically, the Parent-POM defines a variable based SCM string: 
scm:cvs:pserver:u...@[host]:/CVSROOT:${cvs_projectName}.

It resolves in the child project in a SCM string such as this one 
scm:cvs:pserver:u...@[host]:/CVSROOT:CVS_CHILD.

The scm string I get is scm:cvs:pserver:u...@[host]:/CVSROOT:CVS_CHILD/child 
(child being the artifactId of the child project).

(note: artifactId is usually different from the CVS module name)

I tried to set the tagBase to both 
scm:cvs:pserver:u...@[host]:/CVSROOT:CVS_CHILD and 
scm:cvs:pserver:u...@[host]:/CVSROOT:CVS_CHILD/tags but the resulting String 
is the same.

I understand how it works in the SVN paradigm, but does tagBase work for CVS at 
all?

Sébastien Lesaint

-Message d'origine-
De : Lesaint Sébastien [mailto:sebastien.lesa...@ginerativ.fr] 
Envoyé : mardi 27 janvier 2009 15:16
À : Maven Users List
Objet : RE: Does having a parent POM mean the current POM is a module ? (or a 
possible release plugin issue)

Indeed, no, I didn't set the tagBase. Even though I don't understand what it is 
yet, I guess it will solve my problem.

I had seen that when reading the documentation but I though it didn't apply to 
CVS (the SCM we use).

Thanks Baptiste

Sébastien Lesaint 

-Message d'origine-
De : bmat...@gmail.com [mailto:bmat...@gmail.com] De la part de Baptiste MATHUS
Envoyé : mardi 27 janvier 2009 15:07
À : Maven Users List
Objet : Re: Does having a parent POM mean the current POM is a module ? (or a 
possible release plugin issue)

We have a parent pom for the exact kind of things you speak about. But our
projects are not modules (at least not all). So no.
Your problem with scm tag might just be related to the fact you didn't set
the maven-release-plugin tagBase configuration?

See http://maven.apache.org/plugins/maven-release-plugin/usage.html for more
information.

Cheers.

2009/1/27 Lesaint Sébastien sebastien.lesa...@ginerativ.fr

 Hello,

 I want to use a parent POM as a way to easily give some organisation
 specific information to the new projects in our company or the old one being
 mavenized.

 I don't want to declare all the projects of my company as being a module of
 this parent POM. It doesn't make much sense. So the parent POM has no
 modules tag.

 When using the release plugin, though, I realized it is considering the
 project having a parent POM as a module (therefore adding the module name to
 the SCM string).

 So, I am wondering:
  - does having a parent POM make the current POM a module ?
  - If so, how can I implement this organisation POM stuff I need ?
  - If not, is there something wrong with the way I use the release plugin
 or is there an option to avoid the SCM string problem ?

 Thanks for any insight on this matter,

 Sébastien Lesaint


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




-- 
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

-
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: Does having a parent POM mean the current POM is a module ? (or a possible release plugin issue)

2009-01-27 Thread Edelson, Justin

Each project (defined shortly) needs to have the url, scm, and site 
distributionManagement elements defined explicitly.

Project here = 
* Not a module of a parent project
* May or may not have modules within it. 

Justin

-Original Message-
From: Lesaint Sébastien [mailto:sebastien.lesa...@ginerativ.fr] 
Sent: Tuesday, January 27, 2009 9:55 AM
To: Maven Users List
Subject: RE: Does having a parent POM mean the current POM is a module ? (or a 
possible release plugin issue)

Thanks for you answer, Brian.

How do I redefine at the top of my project so that the URLs are generated the 
way I want (not appending the artifactId)?

Sébastien Lesaint


-Message d'origine-
De : Brian E. Fox [mailto:bri...@reply.infinity.nu] Envoyé : mardi 27 janvier 
2009 15:06 À : Maven Users List Objet : RE: Does having a parent POM mean the 
current POM is a module ? (or a possible release plugin issue)

The parent / child relationship != modules. That is a given pom can inherit 
from one parent and be aggregated as a module via another. It is true that 
usually they are the same, but for top level poms (corporate poms or team poms 
we call them) you usually would not have any modules even though everything 
inherits from it.

However, urls are generated using the inheritance tree and each artifactId is 
inserted along the way. If this isn't what you want, then it needs to be 
redefined at the top of your project. Then the modules of that project would 
correctly inherit the url.

-Original Message-
From: Lesaint Sébastien [mailto:sebastien.lesa...@ginerativ.fr]
Sent: Tuesday, January 27, 2009 9:01 AM
To: Maven Users List
Subject: Does having a parent POM mean the current POM is a module ? (or a 
possible release plugin issue)

Hello,

I want to use a parent POM as a way to easily give some organisation specific 
information to the new projects in our company or the old one being mavenized.

I don't want to declare all the projects of my company as being a module of 
this parent POM. It doesn't make much sense. So the parent POM has no modules 
tag.

When using the release plugin, though, I realized it is considering the project 
having a parent POM as a module (therefore adding the module name to the SCM 
string).

So, I am wondering:
 - does having a parent POM make the current POM a module ?
 - If so, how can I implement this organisation POM stuff I need ?
 - If not, is there something wrong with the way I use the release plugin or is 
there an option to avoid the SCM string problem ?

Thanks for any insight on this matter,

Sébastien Lesaint


-
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

AW: [M2] Repository Manager

2009-01-27 Thread Matthias Müller

No, what i wanted to say with way more than i need is that i my initial idea
of a solution wasn't that complex. after reading parts of the reference [1] i
realized that there are useful functionalities (e.g. the user management) i
never concerned so far.
the setup process isn't complex at all, with complex i meant the
functionalities

regards, matthias

[1] http://books.sonatype.com/nexus-book/reference/index.html

- Ursprüngliche Mail
Von: Baptiste MATHUS m...@batmat.net
An: Maven Users List users@maven.apache.org
Gesendet: Dienstag, den 27. Januar 2009, 15:03:30 Uhr
Betreff: Re: [M2] Repository Manager

Cheers.

2009/1/27 Matthias Müller pym...@yahoo.de

Hi Martin,

i installed the nexus repository manager and although it's way more than i
need, it works for my needs.
thanks, matthias

- Ursprüngliche Mail
Von: Martin Höller mar...@xss.co.at
An: Maven Users List users@maven.apache.org
Gesendet: Dienstag, den 27. Januar 2009, 13:29:46 Uhr
Betreff: Re: [M2] Repository Manager

Hi!

You will also find some posts if you search this list's archive with nabble
[2]

hth,
- martin

[0] http://maven.apache.org/repository-management.html
[1]
http://docs.codehaus.org/display/MAVENUSER/Maven%2BRepository%2BManager%2BFeature%2BMatrix
[2] http://www.nabble.com/Maven---Users-f178.html

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

--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

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

Re: Question about excluding parts of parent to be inherited

2009-01-27 Thread kukudas


nvm i found it out myself you can do it with inheritedfalse/inherited.

kukudas wrote:
 
 Is it possible to exclude for example a plugin to be inherited by a child
 which i use in the parent? If so could you give me an example or refere to
 a source where i could read up this feature?
 Thanks in advance for your help kukudas.
 
 edit: Do i understand it right that Profiles don't get inherited btw. ?
 

-- 
View this message in context: 
http://www.nabble.com/Question-about-excluding-parts-of-parent-to-be-inherited-tp21686034p21687550.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: Single MDB in multiple EAR files but different deployment descriptors

2009-01-27 Thread Inman, Peter

I'm not sure if I'm making this far more complex than it actually is,
but if anyone does know what I'm missing with this, I really would
appreciate some pointers.

 

Thanks,Pete

 

From: Inman, Peter 
Sent: 23 January 2009 16:20
To: users@maven.apache.org
Subject: Single MDB in multiple EAR files but different deployment
descriptors

 

Hi,

 

I'm reasonably new to using Maven and am in the process of
re-structuring and migrating my project to the Maven way of doing
things.  So far it's going well, but I have a question which I wonder if
someone could help with.

 

I have a single message driven bean, which I need to be deployed in 4
different EAR files, each with different deployment descriptors. These
deployment descriptors instruct the MDB to attach to different queues,
depending on which EAR it's in and where that EAR is deployed.

 

So, for deployment I have 

 

EAR01.ear

MyMDB.jar

 

EAR02.ear

MyMDB.jar

 

EAR03.ear

MyMDB.jar

 

EAR04.ear

MyMDB.jar

 

 

The only difference between these EAR files, is the deployment
descriptors.

 

Can someone please give me some advice on how to build this using
maven2?

 

Thanks, Pete

AW: Single MDB in multiple EAR files but different deployment descriptors

2009-01-27 Thread Salgar, Mehmet (external)

Hi,

Why are you not building 4 different maven-projects that is containing 4 
different maven-ear-plugins configuration...

I guess this would be the easieszt way... 

Or may be you can write 4 different ear configurations in maven-ear-plugin




T-Mobile Deutschland GmbH
Aufsichtsrat: Hamid Akhavan (Vorsitzender)
Geschäftsführung: Dr. Georg Pölzl (Sprecher), Thomas Berlemann, Jiri 
Dvorjancansky, Philipp Humm,
Dr. Peter Körner, Dr. Raphael Kübler, Günther Ottendorfer, Dr. Steffen Roehn 
Handelsregister: Amtsgericht Bonn, HRB 59 19
Sitz der Gesellschaft: Bonn
WEEE-Reg.-Nr.: DE60800328



-Ursprüngliche Nachricht- 
Von: Inman, Peter [mailto:peterin...@mcpplc.com] 
Gesendet: Dienstag, 27. Januar 2009 16:54
An: users@maven.apache.org
Betreff: RE: Single MDB in multiple EAR files but different deployment 
descriptors

I'm not sure if I'm making this far more complex than it actually is, but if 
anyone does know what I'm missing with this, I really would appreciate some 
pointers.

 

Thanks,Pete

 

From: Inman, Peter
Sent: 23 January 2009 16:20
To: users@maven.apache.org
Subject: Single MDB in multiple EAR files but different deployment descriptors

 

Hi,

 

I'm reasonably new to using Maven and am in the process of re-structuring and 
migrating my project to the Maven way of doing things.  So far it's going well, 
but I have a question which I wonder if someone could help with.

 

I have a single message driven bean, which I need to be deployed in 4 different 
EAR files, each with different deployment descriptors. These deployment 
descriptors instruct the MDB to attach to different queues, depending on which 
EAR it's in and where that EAR is deployed.

 

So, for deployment I have 

 

EAR01.ear

MyMDB.jar

 

EAR02.ear

MyMDB.jar

 

EAR03.ear

MyMDB.jar

 

EAR04.ear

MyMDB.jar

 

 

The only difference between these EAR files, is the deployment descriptors.

 

Can someone please give me some advice on how to build this using maven2?

 

Thanks, Pete

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

[ANN] Properties maven plugin 1.0-alpha-1 Released

2009-01-27 Thread Paul Gier


The Mojo team is pleased to announce the release of the Properties Maven Plugin
version 1.0-alpha-1.

http://mojo.codehaus.org/properties-maven-plugin/

This is the first alpha release of the plugin.

To get this update, simply specify the version in your project's plugin
configuration:

 plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdproperties-maven-plugin/artifactId
   version1.0-alpha-1/version
 /plugin

Regards,

Paul Gier


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

RE: How to do sftp without getting passwd or connection prompt?

2009-01-27 Thread Tang, Ray

Hello:

I have now changed to use scpexe, but still unable to do the
deployment.  The problem is that I followed instructions to generate ssh
keys from this website:  http://cs.smith.edu/FAQ/ssh2.html and I am able
to do ssh remote host (chiadvsdap73) from localhost and backward
without any issues.  I am really puzzled what maven is trying to do here
and there aren't any debugging that I can parse onto build.  

Can someone please shed some light on this simple-but-frustrating issue?

Many Thanks.

Ray



Enclosed is the setting file.

My deploy code looks like this:
target name=distRemoteBinaryRepository if=deploy.official
  artifact:install-provider artifactId=wagon-ssh
version=1.0-alpha-5/
  artifact:localRepository id=repo.local.id
path=${maven.local.repo.dir}/
artifact:deploy file=${dist.artifact.file}
 pom refid=dist.pom.file.id/
 localRepository refid=repo.local.id/
 remoteRepository
url=scpexe://chiadvsdap73/datlib/advantage/sig/repository/snapshot
authentication username=${adv.repo.remote.user}
privateKey=/Net/prduser/users/nbs5u2j/.ssh2/id_dsa_2048_a
passphrase=hitme /
 /remoteRepository
  /artifact:deploy
   /target 


The build log:
[artifact:install-provider] Installing provider:
org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime
[artifact:deploy] Deploying to
scpexe://chiadvsdap73/datlib/advantage/sig/repository/snapshot
[artifact:deploy] Uploading: magma/magma/5.1.0.028/magma-5.1.0.028.jar
to scpexe://chiadvsdap73/datlib/advantage/sig/repository/snapshot
[artifact:deploy] An error has occurred while processing the Maven
artifact tasks.
[artifact:deploy]  Diagnosis:
[artifact:deploy] 
[artifact:deploy] Error deploying artifact 'magma:magma:jar': Error
deploying artifact: Error executing command for transfer
[artifact:deploy] Exit code 78 -
*
[artifact:deploy] ** **
[artifact:deploy] **  This is a private computer system with access  **
[artifact:deploy] **  restricted to those with proper authorization. **
[artifact:deploy] **  If you are not specifically authorized to  **
[artifact:deploy] **  access data on this system, disconnect now.**
[artifact:deploy] **  All information and communications on this **
[artifact:deploy] **  system are subject to review, monitoring, and  **
[artifact:deploy] **  recording at any time without notice or**
[artifact:deploy] **  permission.  Unauthorized use or access may be **
[artifact:deploy] **  subject to prosecution or disciplinary action. **
[artifact:deploy] ** **
[artifact:deploy] *
[artifact:deploy] 
[artifact:deploy] warning:
/Net/prduser/users/nbs5u2j/.ssh2/id_dsa_2048_a: 4: parsing line failed.
[artifact:deploy] Keyboard-interactive:
[artifact:deploy] PAM authentication
[artifact:deploy] Keyboard-interactive:
[artifact:deploy] PAM authentication
[artifact:deploy] Keyboard-interactive:
[artifact:deploy] PAM authentication
[artifact:deploy] Keyboard-interactive:
[artifact:deploy] PAM authentication
[artifact:deploy] Keyboard-interactive:
[artifact:deploy] PAM authentication
[artifact:deploy] Keyboard-interactive:
[artifact:deploy] PAM authentication
[artifact:deploy] Keyboard-interactive:
[artifact:deploy] PAM authentication
[artifact:deploy] Keyboard-interactive:
[artifact:deploy] PAM authentication
[artifact:deploy] Keyboard-interactive:
[artifact:deploy] PAM authentication
[artifact:deploy] warning: Authentication failed.
[artifact:deploy] Disconnected (local); no more authentication methods
available (No further authentication methods available.).
[artifact:deploy] Disconnect reason 14, exit code = 78
[artifact:deploy] 



-Original Message-
From: Johan Lindquist [mailto:jo...@kawoo.co.uk] 
Sent: Friday, January 23, 2009 3:50 PM
To: Maven Users List
Subject: Re: How to do sftp without getting passwd or connection prompt?

Hi Ray,

I may be well off, but this usually works for me - the only thing
different is that I use the scpexe protocol.

Cheers,

Johan

Tang, Ray wrote:
 Can someone please advise how this can get done without entering 
 password or yes?
  
 I am enclosing the settings.xml for reference.
  
 Thanks.
  
 Ray
  
 Here is the output of the logs.
  
 deploy:
  [echo] Deploying foundation to remote 

sftp://nbs5u2j:2xadv103...@chiadvsdap62/datlib/advantage/sig/repository/
snapshot...
 Warning: Reference repo.local.id has not been set at runtime, but was 
 found during build file parsing, attempting to resolve. Future 
 versions of Ant may support  referencing ids defined in non-executed 
 targets.
 [artifact:deploy] Deploying to

Re: Problems with release:prepare on the resolution of a dependency with test classifier

2009-01-27 Thread Thiago Moreira (timba)

  The workaround is not working for me! I tried mvn release:prepare
-DpreparationGoals=clean install without success. Any other thoughts??

On Sun, Jan 25, 2009 at 11:44 PM, Barrie Treloar baerr...@gmail.com wrote:

 On Mon, Jan 26, 2009 at 5:03 PM, Thiago Moreira (timba)
 tmoreira2...@gmail.com wrote:
   Hi there,
 
   I have a multi module project and one of the sub modules produce two
  artifacts: temp-1.2.3.jar and temp-1.2.3-*test*.jar the last one is built
  using this configuration:
 
   plugin
 artifactIdmaven-jar-plugin/artifactId
 executions
 execution
 goals
 goaltest-jar/goal
 /goals
 /execution
 /executions
 /plugin
 
   This second artifact is referenced in another sub module as a compile
  dependency. It works fine for all my development BUT it doesn't work when
  I'm trying to release it. Because the release:prepare goal only executes
 the
  clean verify goals not the install one.

 This is a known problem
 http://jira.codehaus.org/browse/MRELEASE-264

 The workaround is to add to your command line
 -DpreparationGoals=clean install

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

Re: Problems with release:prepare on the resolution of a dependency with test classifier

2009-01-27 Thread Thiago Moreira (timba)

  Ok, I took a look on the source code of the maven-release-plugin and there
is no way to set the preparationGoals from the command line!!!

  The method 
mergeCommandLineConfighttp://maven.apache.org/plugins/maven-release-plugin/xref/org/apache/maven/plugins/release/PrepareReleaseMojo.html#181of
the PrepareReleaseMojo class only merge the releaseVersions and
developmentVersions properties.



On Tue, Jan 27, 2009 at 9:31 AM, Thiago Moreira (timba) 
tmoreira2...@gmail.com wrote:


   The workaround is not working for me! I tried mvn release:prepare
 -DpreparationGoals=clean install without success. Any other thoughts??


 On Sun, Jan 25, 2009 at 11:44 PM, Barrie Treloar baerr...@gmail.comwrote:

 On Mon, Jan 26, 2009 at 5:03 PM, Thiago Moreira (timba)
 tmoreira2...@gmail.com wrote:
   Hi there,
 
   I have a multi module project and one of the sub modules produce two
  artifacts: temp-1.2.3.jar and temp-1.2.3-*test*.jar the last one is
 built
  using this configuration:
 
   plugin
 artifactIdmaven-jar-plugin/artifactId
 executions
 execution
 goals
 goaltest-jar/goal
 /goals
 /execution
 /executions
 /plugin
 
   This second artifact is referenced in another sub module as a compile
  dependency. It works fine for all my development BUT it doesn't work
 when
  I'm trying to release it. Because the release:prepare goal only executes
 the
  clean verify goals not the install one.

 This is a known problem
 http://jira.codehaus.org/browse/MRELEASE-264

 The workaround is to add to your command line
 -DpreparationGoals=clean install

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

Re: Archetype create v. generate

2009-01-27 Thread Dave Newton

Just a ping to see if anybody had any input--I haven't had a chance to 
investigate further yet but need to commit some changes to some 
archetypes and update some documentation soon.


Thanks,
Dave

Dave Newton wrote:
What's the approved way to create archetypes when there's an archetype 
metadata file?


So far it seems like I can either do archetype:create, which (so far) 
isn't shuffling the files around from my archetype metadata file, or 
archetype:generate, which does, but has that interactive bit I'd like to 
avoid.


I think I'm using Version: 2.0-alpha-4, which is actually different from 
the one I *thought* I was using, so I'll re-visit my process and see 
what's currently happening, but I'd still appreciate any input.



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

RE: Re: Archetype expression ${package.replace ('.', '/')} not a valid reference

2009-01-27 Thread Néstor Boscán

Found something.

It looks like the problem is when I'm using JDK 1.4. If I use JDK 5 it works. I 
use JDK 1.4 so I can compile using that version of java because sadly using JDK 
5 and telling the compiler to compile for 1.4 does not work well.

Regards,

Néstor Boscán

-Mensaje original-
De: Raphaël Piéroni [mailto:raphaelpier...@gmail.com] 
Enviado el: Tuesday, January 27, 2009 3:31 AM
Para: Maven Users List
Asunto: [?? Probable Spam] Re: Archetype expression ${package.replace ('.', 
'/')} not a valid reference

Hello Néstor,

Can you please describe a little bit more your problem?
What command line you use? what is the maven/plugin version?
Can you create a JIRA with all these indication.

Thanks,

Raphaël


2009/1/26 Néstor Boscán nestor.bos...@tcs.com.ve:
 Hi



 I've been working with archetypes for a time and I had some archetypes with
 this expression:



 ${package.replace ('.', '/')}



 And it worked, but for some reason now it doesn't work. It throws a warning
 message is not a valid reference.



 Any ideas?





-
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: Re: Archetype expression ${package.replace ('.', '/')} not a valid reference

2009-01-27 Thread Néstor Boscán

Tried to use Maven 2.0.9 and the problem is still there. Tried using 
expressions:

${groupId.replace('.', '/')}
${packageName.replace('.', '/')}

And I'm still getting the same error.

-Mensaje original-
De: Raphaël Piéroni [mailto:raphaelpier...@gmail.com] 
Enviado el: Tuesday, January 27, 2009 3:31 AM
Para: Maven Users List
Asunto: [?? Probable Spam] Re: Archetype expression ${package.replace ('.', 
'/')} not a valid reference

Hello Néstor,

Can you please describe a little bit more your problem?
What command line you use? what is the maven/plugin version?
Can you create a JIRA with all these indication.

Thanks,

Raphaël


2009/1/26 Néstor Boscán nestor.bos...@tcs.com.ve:
 Hi



 I've been working with archetypes for a time and I had some archetypes with
 this expression:



 ${package.replace ('.', '/')}



 And it worked, but for some reason now it doesn't work. It throws a warning
 message is not a valid reference.



 Any ideas?





-
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: Re: Archetype expression ${package.replace ('.', '/')} not a valid reference

2009-01-27 Thread Néstor Boscán

I'm using Maven 2.0.7.

I'm creating an archetype with a spring beanRefContext.xml file that has to 
reference the other spring applicationContext.xml. So I need to create a 
reference in the form:

com/mycompany/myapplication

based on the package. So what I do is to create a Velocity expression 
${package.replace('.', '/')}. 

When I run the mvn archetype:create command with the reference to the archetype 
I get:

${package.replace ('.', '/')} not a valid reference

Néstor

-Mensaje original-
De: Raphaël Piéroni [mailto:raphaelpier...@gmail.com] 
Enviado el: Tuesday, January 27, 2009 3:31 AM
Para: Maven Users List
Asunto: [?? Probable Spam] Re: Archetype expression ${package.replace ('.', 
'/')} not a valid reference

Hello Néstor,

Can you please describe a little bit more your problem?
What command line you use? what is the maven/plugin version?
Can you create a JIRA with all these indication.

Thanks,

Raphaël


2009/1/26 Néstor Boscán nestor.bos...@tcs.com.ve:
 Hi



 I've been working with archetypes for a time and I had some archetypes with
 this expression:



 ${package.replace ('.', '/')}



 And it worked, but for some reason now it doesn't work. It throws a warning
 message is not a valid reference.



 Any ideas?





-
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: Single MDB in multiple EAR files but different deployment descriptors

2009-01-27 Thread Inman, Peter

Thank you, I think this is where I'm getting confused.

I was confusing my actual MDB code + deployment artifact as the same unit, 
therefore in the same project.

What I need to do is generate my MDB code in one project, which outputs a jar, 
then create 4 ear projects which depend on the .jar file which has been created 
from the MDB project.

I had a feeling I was making it more complicated than it was,

Thanks very much for your help.
Pete

-Original Message-
From: Salgar, Mehmet (external) [mailto:mehmet.sal...@external.t-mobile.de] 
Sent: 27 January 2009 16:47
To: Maven Users List
Subject: AW: Single MDB in multiple EAR files but different deployment 
descriptors

Hi,

Why are you not building 4 different maven-projects that is containing 4 
different maven-ear-plugins configuration...

I guess this would be the easieszt way... 

Or may be you can write 4 different ear configurations in maven-ear-plugin




T-Mobile Deutschland GmbH
Aufsichtsrat: Hamid Akhavan (Vorsitzender)
Geschäftsführung: Dr. Georg Pölzl (Sprecher), Thomas Berlemann, Jiri 
Dvorjancansky, Philipp Humm,
Dr. Peter Körner, Dr. Raphael Kübler, Günther Ottendorfer, Dr. Steffen Roehn 
Handelsregister: Amtsgericht Bonn, HRB 59 19
Sitz der Gesellschaft: Bonn
WEEE-Reg.-Nr.: DE60800328



-Ursprüngliche Nachricht- 
Von: Inman, Peter [mailto:peterin...@mcpplc.com] 
Gesendet: Dienstag, 27. Januar 2009 16:54
An: users@maven.apache.org
Betreff: RE: Single MDB in multiple EAR files but different deployment 
descriptors

I'm not sure if I'm making this far more complex than it actually is, but if 
anyone does know what I'm missing with this, I really would appreciate some 
pointers.

 

Thanks,Pete

 

From: Inman, Peter
Sent: 23 January 2009 16:20
To: users@maven.apache.org
Subject: Single MDB in multiple EAR files but different deployment descriptors

 

Hi,

 

I'm reasonably new to using Maven and am in the process of re-structuring and 
migrating my project to the Maven way of doing things.  So far it's going well, 
but I have a question which I wonder if someone could help with.

 

I have a single message driven bean, which I need to be deployed in 4 different 
EAR files, each with different deployment descriptors. These deployment 
descriptors instruct the MDB to attach to different queues, depending on which 
EAR it's in and where that EAR is deployed.

 

So, for deployment I have 

 

EAR01.ear

MyMDB.jar

 

EAR02.ear

MyMDB.jar

 

EAR03.ear

MyMDB.jar

 

EAR04.ear

MyMDB.jar

 

 

The only difference between these EAR files, is the deployment descriptors.

 

Can someone please give me some advice on how to build this using maven2?

 

Thanks, Pete

-
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: Archetype create v. generate

2009-01-27 Thread Raphaël Piéroni

Hi,
One can call the generate goal in batch mode w/
mvn -B archetype:generate -DarchetypeGroupId=...

2009/1/27 Dave Newton newton.d...@yahoo.com:
 Just a ping to see if anybody had any input--I haven't had a chance to
 investigate further yet but need to commit some changes to some archetypes
 and update some documentation soon.

 Thanks,
 Dave

 Dave Newton wrote:

 What's the approved way to create archetypes when there's an archetype
 metadata file?

 So far it seems like I can either do archetype:create, which (so far)
 isn't shuffling the files around from my archetype metadata file, or
 archetype:generate, which does, but has that interactive bit I'd like to
 avoid.

 I think I'm using Version: 2.0-alpha-4, which is actually different from
 the one I *thought* I was using, so I'll re-visit my process and see what's
 currently happening, but I'd still appreciate any input.


 -
 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: Archetype create v. generate

2009-01-27 Thread Dave Newton


Raphaël Piéroni wrote:

One can call the generate goal in batch mode w/
mvn -B archetype:generate -DarchetypeGroupId=...


Oh, I missed that--thanks!

Is it normal that my archetype:create isn't paying attention to the 
archetype-metadata file, or am I missing other things too?


Thanks,
Dave


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

Re: maven / osgi / repositories

2009-01-27 Thread Samuel Le Berrigaud

Hi,

as you point it out there is definitely an issue with the renaming of
groupId /artifactId as it will 'break' maven dependency management.
However I don't think that anyone but the project owner(s) should be
allowed to deploy a jar with their groupId/artifactId (to the public
repo). I believe this is why the springsource guys renamed theirs.

I feel like the issue with non-OSGi jars is very similar to what
happened when first moving all libraries from the maven1 repository to
the maven2 repository. This is even more complicated as this time the
metadata in inside the jar. Until all projects make the effort of
having a correct OSGi compatible MANIFEST in their jars we'll have to
deal with it ourselves.

The only way that I can think of it working is to have your own
repository with OSGi-ified versions of the libraries you need. The
most sensible thing to do is probably changing the version so that it
identifies the jar as being OSGi. This will let you use maven's
dependency management to some extent. You will have to use the
dependencyManagement section of your POMs though to enforce OSGi
versions of the libraries. I don't think those jars can go to the
public repo though.

Practically I would consider creating maven projects on your side of
things using the shade plugin to create an OSGi version of the library
you want, just overriding/merging the MANIFEST and changing the
version. This would simply be a pom.xml and a MANIFEST file.
Another thing is definitely to create issues and provide patches to
those project so that they can start make their jars OSGi compatible.

SaM

On Wed, Jan 28, 2009 at 12:18 AM, Henri Gomez henri.go...@gmail.com wrote:
 Hi Henri,

 it seems to me that OSGi jars are not meant to be anything else that
 traditional jars with extra information in their MANIFEST. I would
 definitely recomment deploying them as standard jar as you would do
 for any normal maven project.

 Simple jar with MANIFEST, but today very few maven artifact are
 OSGIfied, so so should geth OSGIfied jars elsewhere or with a
 different group/artifact id ;(

 One thing that could/would differentiate your OSGi jars is that if you
 use the maven bundle plugin
 [http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html]
 then the pom deployed along side your jar will have the packaging set
 to bundle. To me it seems like enough information.

 For inhouse projects, it's not a problem and we allready do that from
 our RCP projects, but the problem is still here for external projects,
 ie ant, jaxws...

 Another point of reference you might consider is how the springsource
 guys make OSGi-ified version of many java libraries in their bundle
 repository [http://www.springsource.com/repository/]. This acts pretty
 much as a simple maven repository delivering jars.

 I see that but the group/artifact is not the same that the one used in
 developpement, hard after that to get a clean trace from developpment
 to runtime :(

 Also I know that the Felix guys have an initiative around an OSGi
 Bundle Repository (OBR)
 [http://felix.apache.org/site/apache-felix-osgi-bundle-repository.html].
 This is meant to be a repository that is more OSGi specific. I could
 help with dependency resolution -- just as maven does -- by
 introspecting jars MANIFESTs.

 A good idea, it will be nice to get it as maven central.

 And in the long term, get all 'maven' artifact converted to
 osgi-bundle (very long term).

 Or may by specializing maven request, ie I need ant-1.7.2 jar,
 ant-1.7.2 osgi-bundle.
 So we could have simple jar and bundle at the same location in maven repo.

 Archiva or Nexus would most probably satisfy your needs for maven
 repositories. They might become OBRs at some point when OSGi becomes
 more mainstream.

 I think there is plan for this in Nexus.

 Hope this helps,
 SaM

 Thanks for your time Sam, it was helpfull :)

 On Tue, Jan 27, 2009 at 10:24 PM, Henri Gomez henri.go...@gmail.com wrote:
 Hi to all,

 We're using maven to build all our company projects for about 6 months
 and are very happy with it.
 Some of our projects, mainly Eclipse RCP plugins, are also mavenized.

 We know think about OSGIfing more of our projects (server side) and
 track ASF projects Felix of course core but also ServiceMix Kernel.

 BTW, we wonder if there is a consensus or strategy about OSGIfied
 artifacts and their location in external repositories.

 - Should we repackage our current projects to produce both jar and plugins ?

 - How and where to store these artifacts to make sure Felix could get
 it (did a Nexus repository could do the job).

 - How to 'mark' artifacts to indicate the difference between strict
 jar and OSIG jars (bundles). Eclipse prefix then with org.eclipse, SS
 with com.springsource ?


 Advices and experience are more than welcome.

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

Re: maven / osgi / repositories

 as you point it out there is definitely an issue with the renaming of
 groupId /artifactId as it will 'break' maven dependency management.
 However I don't think that anyone but the project owner(s) should be
 allowed to deploy a jar with their groupId/artifactId (to the public
 repo). I believe this is why the springsource guys renamed theirs.

 I feel like the issue with non-OSGi jars is very similar to what
 happened when first moving all libraries from the maven1 repository to
 the maven2 repository. This is even more complicated as this time the
 metadata in inside the jar. Until all projects make the effort of
 having a correct OSGi compatible MANIFEST in their jars we'll have to
 deal with it ourselves.

 The only way that I can think of it working is to have your own
 repository with OSGi-ified versions of the libraries you need. The
 most sensible thing to do is probably changing the version so that it
 identifies the jar as being OSGi. This will let you use maven's
 dependency management to some extent. You will have to use the
 dependencyManagement section of your POMs though to enforce OSGi
 versions of the libraries. I don't think those jars can go to the
 public repo though.

Good idea.

instead of :

groupIdorg.apache.ant/groupId
artifactIdant/artifactId
version1.7.1/version

we could use :

groupIdorg.apache.ant/groupId
artifactIdant/artifactId
version1.7.1-osgi/version

 Practically I would consider creating maven projects on your side of
 things using the shade plugin to create an OSGi version of the library
 you want, just overriding/merging the MANIFEST and changing the
 version. This would simply be a pom.xml and a MANIFEST file.
 Another thing is definitely to create issues and provide patches to
 those project so that they can start make their jars OSGi compatible.

That's a huge task and may be a duplicate works from what is done by
SpringSource and Eclipse ;(

BTW, I'll be happy to see a sample pom.xml for such task, if you have
one, it's more than welcome

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

Release plugin cyclic problem

2009-01-27 Thread Ryan Moquin

I've been struggling with the maven2 release plugin but have managed to get
the majority of my problems except for one.  For some reason when I do a
release on a subproject that I've previously managed to successfully
released before, the maven2 release plugin will keep repeatedly asking me
for the development version of the first project over and over.  It just
does this repeatedly and I cannot progress in releasing the project.. Is
there a bug of some kind that I'm hitting?  This is what the output looks
like:

[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.: Do you want to
resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 1:Project
Dependencies 2:Plugins 3:Reports 4
:Extensions ): (0/1/2/3) 1: : 1
Resolve Project Dependency Snapshots.: 'com.project:service' set to release?
(yes/no
) yes: :
What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
1.2-SNAPSHOT

What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
There are still some remaining snapshot dependencies.: Do you want to
resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 1:Project
Dependencies 2:Plugins 3:Reports 4
:Extensions ): (0/1/2/3) 1: : 1
Resolve Project Dependency Snapshots.: 'com.project:service' set to release?
(yes/no
) yes: : yes
What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
There are still some remaining snapshot dependencies.: Do you want to
resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 1:Project
Dependencies 2:Plugins 3:Reports 4
:Extensions ): (0/1/2/3) 1: : 1
Resolve Project Dependency Snapshots.: 'com.project:service' set to release?
(yes/no
) yes: : What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT:
: Terminate batch job (Y/N)? y

It never asks me for the release version which I thought it always asked me
for first, it just keeps asking for the development version of the first
project and does it over and over repeatedly

Any ideas?

Thanks!

Ryan

Re: Release plugin cyclic problem

2009-01-27 Thread Ryan Moquin

Never mind.. I think I see what happened.. apparently I messed up a version
of a child dependency which became out of sync with everything else.. this
apparently caused the release plugin to go completely haywire.  Telling it I
didn't want to resolve the dependency made the build quit but with an error
telling me what it was trying to resolve (which by fixing manually I think
might allow the release plugin to function properly).

On Tue, Jan 27, 2009 at 8:13 PM, Ryan Moquin fragility...@gmail.com wrote:

 I've been struggling with the maven2 release plugin but have managed to get
 the majority of my problems except for one.  For some reason when I do a
 release on a subproject that I've previously managed to successfully
 released before, the maven2 release plugin will keep repeatedly asking me
 for the development version of the first project over and over.  It just
 does this repeatedly and I cannot progress in releasing the project.. Is
 there a bug of some kind that I'm hitting?  This is what the output looks
 like:

 [INFO] Checking dependencies and plugins for snapshots ...
 There are still some remaining snapshot dependencies.: Do you want to
 resolve them now? (yes/no) no: : yes
 Dependency type to resolve,: specify the selection number ( 0:All 1:Project
 Dependencies 2:Plugins 3:Reports 4
 :Extensions ): (0/1/2/3) 1: : 1
 Resolve Project Dependency Snapshots.: 'com.project:service' set to
 release? (yes/no
 ) yes: :
 What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
 1.2-SNAPSHOT

 What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
 There are still some remaining snapshot dependencies.: Do you want to
 resolve them now? (yes/no) no: : yes
 Dependency type to resolve,: specify the selection number ( 0:All 1:Project
 Dependencies 2:Plugins 3:Reports 4
 :Extensions ): (0/1/2/3) 1: : 1
 Resolve Project Dependency Snapshots.: 'com.project:service' set to
 release? (yes/no
 ) yes: : yes
 What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
 There are still some remaining snapshot dependencies.: Do you want to
 resolve them now? (yes/no) no: : yes
 Dependency type to resolve,: specify the selection number ( 0:All 1:Project
 Dependencies 2:Plugins 3:Reports 4
 :Extensions ): (0/1/2/3) 1: : 1
 Resolve Project Dependency Snapshots.: 'com.project:service' set to
 release? (yes/no
 ) yes: : What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT:
 : Terminate batch job (Y/N)? y

 It never asks me for the release version which I thought it always asked me
 for first, it just keeps asking for the development version of the first
 project and does it over and over repeatedly

 Any ideas?

 Thanks!

 Ryan

Re: Problems with release:prepare on the resolution of a dependency with test classifier

2009-01-27 Thread Barrie Treloar

On Wed, Jan 28, 2009 at 4:34 AM, Thiago Moreira (timba)
tmoreira2...@gmail.com wrote:
  Ok, I took a look on the source code of the maven-release-plugin and there
 is no way to set the preparationGoals from the command line!!!

  The method 
 mergeCommandLineConfighttp://maven.apache.org/plugins/maven-release-plugin/xref/org/apache/maven/plugins/release/PrepareReleaseMojo.html#181of
 the PrepareReleaseMojo class only merge the releaseVersions and
 developmentVersions properties.

We have the same scenario that you have and we are using release fine.

You may want to use
  dependency
groupIdMYGROUP/groupId
artifactIdMYARTIFACT/artifactId
versionMYVERSION/version
typetest-jar/type
scopetest/scope
  /dependency

type = test-jar
instead of classifier = test.

There are some wierd inconsistencies with this.

Straight from our release page in our wiki:
  mvn release:prepare
-Dmaven.scm.provider.cvs.implementation=cvs_native
-DpreparationGoals=clean,install -Dusername=CVS_userid

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

Re: maven / osgi / repositories

2009-01-27 Thread Barrie Treloar

 repositories. They might become OBRs at some point when OSGi becomes
 more mainstream.

One thing I have been toying with for a while is to auto-magically
extend maven-jar-plugin to add the OSGi headers.

I haven't given a lot of thought into what I need to do, but if I
recall correctly, getting a simple OSGified jar isn't much work and if
Maven did this out of the box then the maven repository would become
OSGified over time as projects release their artifacts.

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

m2eclipse CTRL-SHIFT-T Open Type dialog is missing

2009-01-27 Thread Lincoln Baxter, III

Hi Mavenites,

When I install the m2eclipse plugin, version 0.9.6, my Open Type dialog
box disappears. I can't bring it up with a shortcut. The menu item is
gone. It's just missing.
Is this intentional? I really rely on this dialog quite a bit. How can I
get it back?

Thanks,
Lincoln

RE: [M2] Repository Manager