RE: Links to artifacts in a snapshot repository

[Hayes, Peter]

This works:

http://nexus.cedarsoft.com/service/local/artifact/maven/redirect?r=snapshots&g=com.cedarsoft&a=serialization&v=1.0.0-beta2-SNAPSHOT

There is some documentation out there on this though I'm unable to pull it at 
the moment.

These are the parameters:

r = repository name (cannot be a group I'm pretty sure)
g = group Id
a = artifact Id
v = version
p = packaging type
c = classifier

-Original Message-
From: Johannes Schneider [mailto:maili...@cedarsoft.com] 
Sent: Tuesday, December 22, 2009 12:38 PM
To: Maven Users List
Subject: Links to artifacts in a snapshot repository

Hi,

at the moment I am creating a page for a project of mine.
And because not everybody out there uses maven (don't understand why), I
want to provide a link to the latest artifact for manual download.

Of course that is not possible since every snapshot artifact has the
build date prepended.
How could that be solved?


Sincerly,

Johannes


Sample repository:
http://nexus.cedarsoft.com/content/groups/public-snapshots/com/cedarsoft/serialization/1.0.0-beta2-SNAPSHOT/

-
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: obtain latest snapshot to put on website for auto-update?

[Hayes, Peter]

You can use this url:

http://:/nexus/service/local/artifact/maven/redirect?r=&g=&a=&v=&p=

Nexus will handle the SNAPSHOT conversion to latest so you don't need to read 
the metadata or anything like that.

Peter

-Original Message-
From: James Russo [mailto:j...@halo3.net] 
Sent: Friday, November 13, 2009 1:29 PM
To: Maven Users List
Subject: Re: obtain latest snapshot to put on website for auto-update?

Wayne,

Thanks for your reply. I had thought the repo spec was fairly  
standardized by maven, so regardless of repo manager I might be able  
to accomplish this.  I will post it on the nexus user list though for  
more input.

I think maybe the simplest solution would be to write a script to  
authenticate against nexus (the HTTP based repo really), fetch the  
maven-metadata.xml file which appears to have info on the latest  
snapshot for a specific artifact and fetch it from there.

-jr


On Nov 13, 2009, at 11:12 AM, Wayne Fay wrote:

>> nexus to grab the latest snapshot and copy this to webserver? Is  
>> there a
> ...
>> special "latest snapshot" link available in nexus or must I  
>> download the
>
> You do know about the Nexus User list, right? As a percentage of
> users, maybe 15% of the Maven Users know anything about Nexus, vs
> ~100% of those on Nexus Users list.
>
>> Perhaps I should just setup a simple no artifacts pom file which  
>> lists the
>> artifact as a dependency and let that maven grab it for me?
>
> Sounds like a reasonable solution. Otherwise this sounds like a good
> feature request for Nexus.
>
> 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


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

RE: Centralized build configuration: Improvements in 2.2?

[Hayes, Peter]

Instead of profiles could you configure the various plugins in the
pluginManagement[1] section of your parent pom(s) and then just enable
the plugin in the various project poms?

[1]
http://www.sonatype.com/books/maven-book/reference/optimizing-sect-plugi
ns.html

-Original Message-
From: Lewis, Eric [mailto:eric.le...@ipi.ch] 
Sent: Monday, August 17, 2009 11:08 AM
To: Maven Users List
Subject: Centralized build configuration: Improvements in 2.2?

Hi

We have a standard build, but some modules need special build steps,
like JAXB or OSGi stuff etc.
In order to stick to DRY (Don't Repeat Yourself), we defined profiles in
the parent POM which add the required plugins to the build.

So for instance, to build something with JAXB, we call 'mvn clean
package -Pjaxb'

As nice as this is, it totally breaks as soon as we try to build the
whole project with the Maven Reactor. It's not possible just to specify
'mvn clean package' for the top-level POM and to expect the profiles to
be called magically.

We've tried many things, but with 2.0.9 there wasn't any satisfying
solution.

Now, before I go into every POM and add build steps by copy & paste: Has
this situation become better with Maven 2.2? For instance:
- Can I import XML fragments into a POM?
- Can I activate profiles by some other means? I remember profile
properties file, but I think that didn't work.
- Any other or better ideas?

Thanks & best regards,
Eric
-
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: LATEST and RELEASE release version management

[Hayes, Peter]

Version ranges seem to totally break reproducibility of released builds.


Personally, I'd like to see these eliminated from Maven altogether and
replaced with a separate version compatibility field that indicates
which versions of a dependency you are compatible with but still have a
specific version that you declare:

...

  org.springframework
  spring-core
  2.5.5
  [2.5,3.0-!)

...

This would ensure reproducibility while providing higher value version
information that could then be used within metadata and leveraged by
containers such as OSGI.

Pete

-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
Sent: Wednesday, April 08, 2009 3:16 AM
To: Maven Users List
Cc: Maven Users List
Subject: Re: LATEST and RELEASE release version management

sounds like you want version ranges

[1.0,2.0-!)

Sent from my [rhymes with myPod] ;-)

On 8 Apr 2009, at 01:39, Tim  wrote:

> http://jira.codehaus.org/browse/MNG-4089
> I need to read over the bug that was linked as a duplicate more  
> closely but
> I don't think it's the same thing.
> What I asked for was the same as what you said with 1.0-LATEST.
> Doing something like that or 1.0-RELEASE would actually be very  
> beneficial
> to people that know that minor releases won't break backwards  
> compatibility
> but will allow for more features without having to keep changing  
> versions.
>
> On Mon, Apr 6, 2009 at 6:29 PM, Brian E. Fox  
> wrote:
>
>> Having the release plugin translate these values at release time
>> _before_ the validation build and tag is the only sane way to use  
>> them.
>> I currently have never use them because they aren't repeatable.
>>
>>
>>
>> From: Hayes, Peter [mailto:peter.ha...@fmr.com]
>> Sent: Monday, April 06, 2009 12:12 PM
>> To: Maven Users List
>> Subject: RE: LATEST and RELEASE release version management
>>
>>
>>
>> Graham Leggett wrote:
>>
>>> Having said that, it makes no sense to have the release plugin care
>>> about LATEST, because by definition, building against LATEST isn't
>>> repeatable, and in order for there to be a release, you need the  
>>> build
>>> to be repeatable.
>>
>> I think this does impact the release plugin as it could offer the
>> ability to resolve the LATEST version at release time.  These builds
>> would be reproducible because the release plugin tags the poms during
>> the release process.
>>
>> I think what you're saying is that the build prior to the release  
>> build
>> is not guaranteed to have the same dependent artifacts as the release
>> build.  I care about the release build being reproducible.
>>
>> Pete
>>
>>
>
>
> -- 
>
> Emo Philips
<http://www.brainyquote.com/quotes/authors/e/emo_philips.html 
> >
> - "A computer once beat me at chess, but it was no match for me at
> kick
> boxing."

-
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: LATEST and RELEASE release version management

[Hayes, Peter]

rtf1uqccPrltQ.rtf
Description: RTF file


smime.p7s
Description: S/MIME cryptographic signature

LATEST and RELEASE release version management

[Hayes, Peter]

We use Maven in an enterprise environment and internally we are required
to execute "release" builds whenever we want to install to our testing
environment.  We have found that executing many release builds can be
tedious when we have in-development snapshot dependencies that also have
to be released.  We don't mind doing the releases, but the manual
version update -- release -- revert version cycle is a chore.

I was hoping that Maven could simplify this by allowing a project to
declare a dependency on LATEST or 1.0-LATEST and have the maven release
plugin resolve this to the actual latest released version available in
the repository.  The subsequent fully resolved pom would then be
uploaded to the internal repository and the pom left in source control
still references LATEST.  

Does maven already support something like this or would others find this
useful?

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology 

RE: Central index redirect

[Hayes, Peter]

We are using Nexus so I added the 'exist' repository as a mirror to
central.  The download indexes scheduled task though still receives an
error but I can't tell if it is actually trying to download from central
or the mirror.   

-Original Message-
From: Brian E. Fox [mailto:bri...@reply.infinity.nu] 
Sent: Thursday, April 02, 2009 11:01 PM
To: Maven Users List
Subject: RE: Central index redirect

We moved the index to S3 back in November to reduce the load on Central
and improve access time for other artifacts. (224m downloads and 24TB
last month alone for the index) The index is not accessible from
repo1.maven.org anymore and it redirects to S3. (the s3 url is pseudo
dynamic so to get the files you must still hit central for the
redirected url).

If you can't use s3, then you'll have to change to ibiblio or another
mirror that is hosting the index files directly. If you use Nexus, then
the mirror support[1] will allow you to use ibiblio and repo1
transparently at the same time and the index would come from ibiblio. 

[1]
http://www.sonatype.com/people/2009/03/new-feature-in-nexus-13-mirror-su
pport/

-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
Sent: Thursday, April 02, 2009 4:30 PM
To: Maven Users List
Subject: Re: Central index redirect

setup nexus and pull off a mirror of repo1

2009/4/2 Hayes, Peter 

> The company that I work for has blocked all access to the Amazon S3
> hosting site due to security / threat concerns.   Due to this, I am no
> longer able to download the central index. Has anyone else had this
> issue and if so were they able to work around it?
>
> Peter Hayes
> Architecture & Shared Technology Services | Fidelity Investments
> Management Technology
>
>
>

-
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

Central index redirect

[Hayes, Peter]

The company that I work for has blocked all access to the Amazon S3
hosting site due to security / threat concerns.   Due to this, I am no
longer able to download the central index. Has anyone else had this
issue and if so were they able to work around it?

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology 

Changes plugin accessing an Integrated Windows Authenticated JIRA instance

[Hayes, Peter]

We have JIRA running in a container that uses IWA for authenticating the
web client.  I'd like to take advantage of the maven-changes-plugin to
generate a change report from JIRA but it complains with the following
error :

Dec 6, 2008 12:29:02 PM
org.apache.commons.httpclient.auth.AuthChallengeProcessor
selectAuthScheme
INFO: ntlm authentication scheme selected
Dec 6, 2008 12:29:02 PM org.apache.commons.httpclient.HttpMethodDirector
processWWWAuthChallenge
INFO: No credentials available for NTLM @..com:443
[ERROR] Unable to extract a JIRA pid from the page at the url
https://..com/browse/X

Has anyone successfully accomplished this?

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology 

"mvn site" tries to access central

[Hayes, Peter]

We use an internal repository to proxy central and therefore don't
configure maven to directly connect to the internet.  When I run mvn
site, I always get a warning that http://repo1.maven.org/maven2 is
invalid and will be blacklisted.  It seems that the site generation
plugin tries to directly access this url.  Is there a way for the site
plugin to instead use the mirror defined in the settings.xml?

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology 

Release plugin : Update RELEASE versions to actual release version during prepare

[Hayes, Peter]

We are considering trying to use the special RELEASE version in our pom
files.  I think in order to generate reproducible builds though the
RELEASE version needs to be locked down to the actual latest release
version as specified in the metadata.  Once the release has been
performed, the version change should be reverted back to RELEASE.  
 
Is this part of the release plugin functionality?

Peter Hayes    
Architecture & Shared Technology Services | Fidelity Investments
Management Technology 

 

RE: WSDL as Maven artifact

[Hayes, Peter]

Thanks for the info.  I will plan on using your process.

Pete 

-Original Message-
From: Paul [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 09, 2008 4:37 PM
To: users@maven.apache.org
Cc: Hayes, Peter
Subject: Re: WSDL as Maven artifact

I second Kalle about the fact that wsdl are too small entities to elect them 
artifacts. In my current project I keep the wsdl in the service 
implementation artifact and I package the wsdl with clients stubs in another 
artifact. The client artifact being built with the following sequence : 
unpack the wsdl from the service artifact using maven-dependency-plugin and 
then generate the client stubs with the appropriate maven plugin.

Paul

Le Thursday 09 October 2008 19:02:45 Hayes, Peter, vous avez écrit :
> We are building web services and in our approach multiple maven projects
> would be consumers of the service WSDL in order to generate their server
> / client stubs.  I think it would be good to have a project of packaging
> type wsdl and then have consumer projects depend on that artifact.  Has
> anybody tried to do this or is there a better pattern for doing this?
>
> I found one reference on the web about this :
>
> http://myarch.com/using-maven-repository-as-web-services-registry
>
> Possibly the hard part would be integrating with existing wsdl2java
> plugins that expect a file path to the WSDL file.  I would guess that I
> would have to customize one to automatically grab depencies of type wsdl
> and then pass them to the code generator.
>
>
> Peter Hayes   <http://www.linkedin.com/in/petehayes>
> Architecture & Shared Technology Services | Fidelity Investments
> Management Technology




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: WSDL as Maven artifact

[Hayes, Peter]

How do you end up generating the server side skeleton files?  Is this
done as part of the module with the WSDL? 

-Original Message-
From: Kalle Korhonen [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 09, 2008 3:00 PM
To: Maven Users List
Subject: Re: WSDL as Maven artifact

I think in typical cases a single WSDL is too small of a source fragment
to
be a build artifact. The pattern I've often followed is that I keep the
wsdl
and the generated client stubs in one module with an obvious packaging
type
jar, then use the jar both on the client and the server side.

Kalle


On Thu, Oct 9, 2008 at 10:02 AM, Hayes, Peter <[EMAIL PROTECTED]>
wrote:

>  We are building web services and in our approach multiple maven
projects
> would be consumers of the service WSDL in order to generate their
server /
> client stubs.  I think it would be good to have a project of packaging
type
> wsdl and then have consumer projects depend on that artifact.  Has
anybody
> tried to do this or is there a better pattern for doing this?
>
> I found one reference on the web about this :
>
> http://myarch.com/using-maven-repository-as-web-services-registry
>
> Possibly the hard part would be integrating with existing wsdl2java
plugins
> that expect a file path to the WSDL file.  I would guess that I would
have
> to customize one to automatically grab depencies of type wsdl and then
pass
> them to the code generator.
>
>
> Peter Hayes [image: LinkedIn
Profile]<http://www.linkedin.com/in/petehayes>
> Architecture & Shared Technology Services | Fidelity Investments
Management
> Technology
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

WSDL as Maven artifact

[Hayes, Peter]

We are building web services and in our approach multiple maven projects
would be consumers of the service WSDL in order to generate their server
/ client stubs.  I think it would be good to have a project of packaging
type wsdl and then have consumer projects depend on that artifact.  Has
anybody tried to do this or is there a better pattern for doing this?
 
I found one reference on the web about this :
 
http://myarch.com/using-maven-repository-as-web-services-registry
 
Possibly the hard part would be integrating with existing wsdl2java
plugins that expect a file path to the WSDL file.  I would guess that I
would have to customize one to automatically grab depencies of type wsdl
and then pass them to the code generator.  
 

Peter Hayes    
Architecture & Shared Technology Services | Fidelity Investments
Management Technology 

 

RE: Release Plugin - Using partial functionality of the prepare goal

[Hayes, Peter]

You can hack together a new plugin pretty quickly that uses the
maven-release-manager components to achieve what you need.  We did this
in order to integrate a release mechanism into our Hudson build server. 

-Original Message-
From: Dan Tran [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 04, 2008 12:38 PM
To: Maven Users List
Subject: Re: Release Plugin - Using partial functionality of the prepare
goal

On Thu, Sep 4, 2008 at 8:58 AM, Scott Carter <[EMAIL PROTECTED]>
wrote:
> I am a newbie to using the release plugin, but I have a need to use
just
> part of the functionality of the release:prepare goal.  How can this
be
> done?  I have read the optional arguments and do not see a way to do
this.
> For example I might need to
>
> *  Just check that there are no snapshot dependencies without running
the
> rest of the logic

cant

> *  Run the release:prepare logic without updating the trunk pom
versions

-DdryRun=true

> *  Run just the tag logic
>

use maven-scm-plugin with scm:tag goal


> Are these things possible, and if so, please a little help on how to
do
> this.  I will not get into the philosophical reasoning for this, but
it is
> necessary to fit our internal process.  Thanks in advance for the
help.
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: build fails

[Hayes, Peter]

Sorry - I only have experience with Maven 2.

Pete 

-Original Message-
From: radiya sojitrawala [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 25, 2008 12:28 PM
To: Maven Users List
Subject: Re: build fails

hi Peter,

I am using Maven 1.1. I dotn see a settings.xml

-R

On Wed, Jun 25, 2008 at 9:16 AM, Hayes, Peter <[EMAIL PROTECTED]>
wrote:

> If you are behind a firewall, make sure to configure the proxy
settings
> :
>
> http://maven.apache.org/guides/mini/guide-proxies.html
>
> If that's not the problem, please post the full output.
>
> Pete
>
> -Original Message-
> From: radiya sojitrawala [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 24, 2008 7:57 PM
> To: users@maven.apache.org
> Subject: build fails
>
> Hi,
>
>
>
> I ma new to Maven. My build fails due to the following:
>
>
>
>
>
> >> The build cannot continue because of the following unsatisfied
> dependencies:
>
> - org.codehaus.plexus:plexus-utils:1.0.5:jar
>
> - com.jcraft:jsch:0.1.27:jar
>
> - org.apache.velocity:velocity:1.5:jar
>
> - org.apache.maven.wagon:wagon-provider-api:1.0-beta-2:jar
>
> - org.apache.maven.wagon:wagon-http:1.0-beta-2:jar
>
> - org.apache.maven.wagon:wagon-ftp:1.0-beta-2:jar
>
> - org.apache.maven.wagon:wagon-ssh-common:1.0-beta-2:jar
>
> - org.apache.maven.wagon:wagon-ssh:1.0-beta-2:jar
>
> - org.apache.maven.wagon:wagon-ssh-external:1.0-beta-2:jar
>
> - org.apache.maven.wagon:wagon-file:1.0-beta-2:jar
>
> - net.java.dev.stax-utils:stax-utils:20060502:jar
>
>
>
> Any pointers?
>
> Thanks
>
> Radiya
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: build fails

[Hayes, Peter]

If you are behind a firewall, make sure to configure the proxy settings
:

http://maven.apache.org/guides/mini/guide-proxies.html

If that's not the problem, please post the full output.

Pete 

-Original Message-
From: radiya sojitrawala [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 24, 2008 7:57 PM
To: users@maven.apache.org
Subject: build fails

Hi,



I ma new to Maven. My build fails due to the following:





>> The build cannot continue because of the following unsatisfied
dependencies:

- org.codehaus.plexus:plexus-utils:1.0.5:jar

- com.jcraft:jsch:0.1.27:jar

- org.apache.velocity:velocity:1.5:jar

- org.apache.maven.wagon:wagon-provider-api:1.0-beta-2:jar

- org.apache.maven.wagon:wagon-http:1.0-beta-2:jar

- org.apache.maven.wagon:wagon-ftp:1.0-beta-2:jar

- org.apache.maven.wagon:wagon-ssh-common:1.0-beta-2:jar

- org.apache.maven.wagon:wagon-ssh:1.0-beta-2:jar

- org.apache.maven.wagon:wagon-ssh-external:1.0-beta-2:jar

- org.apache.maven.wagon:wagon-file:1.0-beta-2:jar

- net.java.dev.stax-utils:stax-utils:20060502:jar



Any pointers?

Thanks

Radiya


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Release plugin does not change version of plugin's dependency even though it is in reactor

[Hayes, Peter]

No this is not the issue.  The problem is that the version of the build
tool artifact does not get updated during the release:prepare phase.  

Pete

-Original Message-
From: Kalle Korhonen [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 18, 2008 10:11 PM
To: Maven Users List
Subject: Re: Release plugin does not change version of plugin's
dependency even though it is in reactor

(If I understand your problem correctly) by default release:prepare
doesn't
run install goal which can cause issues like this, but you can configure
which preparation goals need to be run (also see my comment below from
our
build why we need it):

org.apache.maven.plugins
maven-release-plugin


clean install

Kalle

On Wed, Jun 18, 2008 at 5:46 PM, Hayes, Peter <[EMAIL PROTECTED]>
wrote:

> I am using the checkstyle plugin for a multi-module build.  As
directed
> in the checkstyle documentation, I configured the checkstyle plugin to
> include a dependency on one of my sub projects like this :
>
>...
>  
>org.apache.maven.plugins
>maven-checkstyle-plugin
>
>  
>com.example.whizbang
>build-tools
>1.0-SNAPSHOT
>  
>
>  
>...
>
> When running a release build, the reference to the build tools version
> does not get updated to the target release version, even though the
> build-tools project is a sub-module of the project.
>
> Could the release plugin be enhanced to update this version?
>
> Checkstyle doc :
>
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-m
>
odule-config.html<http://maven.apache.org/plugins/maven-checkstyle-plugi
n/examples/multi-module-config.html>
>
> Thanks,
>
> Peter Hayes
> Architecture & Shared Technology Services | Fidelity Investments
> Management Technology
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Release plugin does not change version of plugin's dependency even though it is in reactor

[Hayes, Peter]

Wendy wrote:
> Generally when I have plugins or tools that I use during the build, I
> release them separately and in advance of the project build.  (And,
> how often are the checkstyle rules going to change?)

Yes, this is probably the workaround I'd use.

> If you're going to leave this as a module in the build, you might try
> using ${project.version} as the .

We originally had this but it caused a problem.  It seemed that the
${project.version} was resolved to the current executing project's
version instead of the version of the project that the plugin was
declared in.

>From your email, I guess this would not be a feature that you think
would be worth adding to the release plugin.

Thanks,

Peter



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Release plugin does not change version of plugin's dependency even though it is in reactor

[Hayes, Peter]

I am using the checkstyle plugin for a multi-module build.  As directed
in the checkstyle documentation, I configured the checkstyle plugin to
include a dependency on one of my sub projects like this :

...
  
org.apache.maven.plugins
maven-checkstyle-plugin

  
com.example.whizbang
build-tools
1.0-SNAPSHOT
  

  
...

When running a release build, the reference to the build tools version
does not get updated to the target release version, even though the
build-tools project is a sub-module of the project.

Could the release plugin be enhanced to update this version?

Checkstyle doc :
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-m
odule-config.html

Thanks,

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Axis2 and Maven2

[Hayes, Peter]

I use the following dependencies with axis 2:


org.apache.axis2
axis2-jaxws
1.4


org.apache.axis2
axis2-adb
1.4


Pete 

-Original Message-
From: Karl Heinz Marbaise [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 28, 2008 5:43 AM
To: Maven Users List
Subject: Axis2 and Maven2

Hello,

i have a pom which defines a phase to create an WSDL from Java code...

The following part in my POM i have added to have the PlugIn:

   
org.apache.axis2.maven2
axis2-java2wsdl-maven-plugin
1.1

com.soebes.testaxis2.service.WeatherService
HelloImpl.ws
http://testaxis2.weatherservice
http://testaxis2.weatherservice




java2wsdl




.

The dependency part:
   
axis
axis
1.4



But all times a run the mvn compile i got the following output:

Downloading: http://repo1.maven.org/maven//jaxen/poms/jaxen-1.1-beta-10.pom
Downloading:
http://ws.zones.apache.org/repository//jaxen/poms/jaxen-1.1-beta-10.pom
Downloading:
http://repo1.maven.org/maven2/jaxen/jaxen/1.1-beta-10/jaxen-1.1-beta-10.pom
Downloading:
http://repository.atlassian.com/maven2/jaxen/jaxen/1.1-beta-10/jaxen-1.1-beta-10.pom
Downloading:
http://svn.atlassian.com/svn/public/contrib/repository/maven2/jaxen/jaxen/1.1-beta-10/jaxen-1.1-beta-10.pom
Downloading:
https://maven-repository.dev.java.net/nonav/repository//jaxen/poms/jaxen-1.1-beta-10.pom
Downloading:
http://repo1.maven.org/maven2/jaxen/jaxen/1.1-beta-10/jaxen-1.1-beta-10.pom
[INFO] [axis2-java2wsdl:java2wsdl {execution: default}]
java.lang.Exception: java.lang.ClassNotFoundException:
com.soebes.testaxis2.service.WeatherService
at
org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.generate(Java2WSDLCodegenEngine.java:58)
at
org.apache.axis2.maven2.java2wsdl.Java2WSDLMojo.execute(Java2WSDLMojo.java:146)


So my question is: Does someone has a running POM with Axis2 (1.4)
...running ?

Or does someone here has a suggestions?

Thanks in advance.

Kind regards
Karl Heinz Marbaise
-- 
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen   http://www.soebes.de

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Sonatype's Nexus 1.0-beta-1 Released

[Hayes, Peter]

What do you mean by not relying on a CMS?  Does that mean an application server?

I was looking through the documentation and it does not look like Nexus is made 
to be hosted within an application server like Tomcat and Websphere.  Is that 
right?

Thanks,

Pete

-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 03, 2008 1:46 PM
To: Maven Users List
Subject: Re: Sonatype's Nexus 1.0-beta-1 Released 

Hi,

We will make a comparison table but I'll try to summarize the  
technical and non-technical.

Technical
- We use ExtJS for the front-end
- The ExtJS client talks to the back-end using REST via RESTLet, so  
everything is accessed via a REST API
- We rely on no CMS, which we don't believe is a real benefit as we  
want to go right down to the bare metal to be able to adapt for  
clustering, failover, federated querying and a few other cool things  
we're working on. We use the filesystem and lucene and that's it.
- The core of Nexus uses the same components and libraries as Maven  
itself.
- Full integration with Eclipse via m2eclipse. Tamas and Eugene work  
very closely together to provide seamless integration.
- The other IDEs are also following suite, so Netbeans is also  
focusing on Nexus (even if they have pluggable providers) and Eugene  
is currently working with JetBrains to integrate Nexus indices with  
IntelliJ

Non-Technical
- We have 3 FTEs currently working on Nexus
- Nexus will soon have full commercial support and training
- We are testing Nexus with some of the largest dev organizations  
there are
- Nexus will be going through full usability testing at one of the  
best HCI labs in the world
- We have 3 core Maven folks (myself, brian, and john) working with  
clients, users, and other open source organizations to help solve our  
metadata problems once and for all.

That's it in nutshell, but we'll make a full comparison and put it on  
the Nexus website.

On 3-Apr-08, at 10:00 AM, BlueBerry wrote:
> Dear Jason
>could you tell me what difference is between Artifactory and nexus.
>
> thanks a lot
>
> thomas.chen
>
> - Original Message -
> From: "Jason van Zyl" <[EMAIL PROTECTED]>
> To: "Maven Developers List" <[EMAIL PROTECTED]>; "Maven Users  
> List" ; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED] 
> >; <[EMAIL PROTECTED]>
> Sent: Thursday, April 03, 2008 6:22 PM
> Subject: Sonatype's Nexus 1.0-beta-1 Released
>
>
> Dear Jolly Maven Users,
>
> After many months of alpha testing we are tickled pink to announce the
> 1.0-beta-1 release of Nexus. Tamás Cservenák, Brian Fox, Eugene
> Kuleshov and Justin Richard have been working very hard to bring Maven
> users something we feel will benefit the whole community. In an
> unbelievable twist of fate, this might be the first Maven-related
> project that actually has documentation with its first releases! We
> have a website with some information about Nexus which you can find
> here:
>
> http://nexus.sonatype.org
>
> And Tim O'Brien has written a chapter on Maven repository management
> which covers all the basics that people will need to get started with
> Nexus. We'll have a few more cool announcements to make about Nexus
> shortly, but people are probably most interested in how to get
> started, where they can download Nexus, and if there are any mailing
> lists to join. You can surf around the site, but here are the most
> relevant links.
>
> http://nexus.sonatype.org/getting-started.html
> http://nexus.sonatype.org/download.html
> http://nexus.sonatype.org/mailing-lists.html
>
> We look forward to feedback from users, and you'll definitely be
> hearing more from us about Nexus!
>
> Thanks,
>
> The Sonatype Team
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> jason at sonatype dot com
> --
>
> Selfish deeds are the shortest path to self destruction.
>
> -- The Seven Samuari, Akira Kirosawa 
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
--

What matters is not ideas, but the people who have them. Good people  
can fix bad ideas, but good ideas can't save bad people.

-- Paul Graham 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Nexus repository manager

[Hayes, Peter]

I did not know Nexus was going to be commercial.  Thanks for the info.

Pete 

-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 12, 2008 5:30 PM
To: Maven Users List
Subject: Re: Nexus repository manager

Nexus is a commercial product from Sonatype, so you should probably
contact them via their website for more information.

If you are interested in snapshot cleanup that works today, you might
try Archiva: http://maven.apache.org/archiva/ :)

Cheers,
Brett

On 13/02/2008, Hayes, Peter <[EMAIL PROTECTED]> wrote:
> Is there any update on the Nexus repository manager?  I am interested
in
> snapshot cleanup.
>
> Thanks,
>
> Peter Hayes
> Architecture & Shared Technology Services | Fidelity Investments
> Management Technology
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Nexus repository manager

[Hayes, Peter]

Is there any update on the Nexus repository manager?  I am interested in
snapshot cleanup.

Thanks,

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Use 1.6 JRE globally

[Hayes, Peter]

You may want to look at using the enforcer plugin :

http://maven.apache.org/plugins/maven-enforcer-plugin/

This would allow you to guarantee that the jdk running is the build's required 
JDK.  

As to your initial question, I agree that the only way to set the JDK versino 
globally in Maven is to execute Maven with the JDK home set to the VM you 
require.  Otherwise you are going to have to configure individual plugins (like 
surefire) to point to the path of the VM that you require.  This is not 
portable and should be avoided.

Pete 

-Original Message-
From: Michael [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 16, 2008 11:51 AM
To: Maven Users List
Subject: Re: Use 1.6 JRE globally

Olivier Serve wrote:
> Le mercredi 16 janvier 2008, Michael a écrit :
>> Olivier Serve wrote:
>>> Hi _o/
>>>
>>> I have a little project that requires a JDK 1.6 (it uses some 1.6 specific 
>>> APIs).
>>> I have both Java 1.5 and 1.6 installed on my system to do some tests.
>>>
>>> Using the following, I can build the artifact.
>>> --8<--
>>> 
>>>   ...
>>>   
>>> 
>>>   
>>> maven-compiler-plugin
>>> 
>>>   1.6
>>>   true
>>>   1.6
>>>   1.6
>>> 
>>>   
>>> 
>>>   
>>>   ...
>>> 
>>> --8<--
>>>
>>> However, the tests fail to execute with a "Bad version number in .class 
>>> file".
>>> OK, the surefire plugin must be using the 1.5 JRE to execute the tests and 
>>> thus fails.
>>> There must be a way to tell it to use a 1.6 JRE and that would solve my 
>>> problem.
>>>
>>> But I find it quite a bad precatice to have to state in two locations that 
>>> I need a 1.6 jre.
>>> Is there a way to tell maven to use a JRE 1.6 for all Java-related things 
>>> in a single location ?
>> set JAVA_HOME JRE_HOME correctly
> 
> No, because doing this will make the build non-reproducible on other 
> environments as I will lose the 1.6 requirement.

you could set i temporary for the each maven instance

-- 
 OOXML - Say NO To Microsoft Office broken standard
http://www.noooxml.org


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Newbie: libraries out of date in repository

[Hayes, Peter]

I think you may be barking up the wrong tree here.  The m2eclipse plugin
ships with its own snapshot of the versions available in the public
repository.  It does not go out to the repositories in real time to
support the "Add Dependency" feature.  See the m2eclipse documentation
for more information.

Pete 

-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Sent: Sunday, January 13, 2008 11:47 PM
To: Maven Users List
Subject: Re: Newbie: libraries out of date in repository

On Jan 13, 2008 8:31 PM, Chris <[EMAIL PROTECTED]> wrote:

> Thanks. I'm finding that quite few of the libraries I need are out of
> date or incomplete (or scattered in several different places and
> completely disorganized).
>
> How, in general, can I solve this problem without being dependent on
the
> dev team for each library?
>
> Can I create my own repository someplace on our internal network so
that
> all our developers at my company can point at a clean, well-organized
> common repository? Or can I alter the main maven repository somehow?

While it's more trouble up front, working with the project developers
to get the libraries into the central repo is the best thing for the
community.  If the project developers aren't interested, you can
submit things for upload [1].

In addition to that, it's a very good idea to establish your own
internal repositories.   One of the repository managers such as
Archiva, Proximity or Artifactory can be very useful here, especially
if you want to proxy the various remote repos you're using.

[1]
http://maven.apache.org/guides/mini/guide-central-repository-upload.html

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Multi-module deploy results in partial deployment on module build failure

[Hayes, Peter]

Interesting.  We are planning on using snapshot builds.  What are the
issues you have faced? 

-Original Message-
From: Michael McCallum [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 04, 2007 3:24 PM
To: Maven Users List
Subject: Re: Multi-module deploy results in partial deployment on module
build failure

try a build process that does not involve deploying snapshots, it will
make 
your life a _lot_ easier

On Friday 05 October 2007 03:32, Hayes, Peter wrote:
> I have noticed that during a multi-module deploy build it is possible
> that poms / artifacts are deployed to the repository even if a
> subsequent module fails and the build is stopped.  This seems to be
> suboptimal (from my perspective).  Are there any thoughts about making
> this an all-or-nothing function?
>
> Peter Hayes
> Architecture & Shared Technology Services | Fidelity Investments
> Management Technology

-- 
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Multi-module deploy results in partial deployment on module build failure

[Hayes, Peter]

I have noticed that during a multi-module deploy build it is possible
that poms / artifacts are deployed to the repository even if a
subsequent module fails and the build is stopped.  This seems to be
suboptimal (from my perspective).  Are there any thoughts about making
this an all-or-nothing function?

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology

RE: checkstyle plugins: maven and eclipse

[Hayes, Peter]

In my organization we have created a super pom that all projects inherit
from.  Within that super pom, we have configured the eclipse plugin to
generate a standard .checkstyle file that includes the same rules that
are applied by the maven build.  This works well but you do have to keep
the two in sync.

See :
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#a
dditionalConfig

-Original Message-
From: houzecl [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 04, 2007 4:02 AM
To: users@maven.apache.org
Subject: Re: checkstyle plugins: maven and eclipse


Yes, the last part of your post is what we'd like to do:

One mavenized projet holding a set of configuration files.
So that you can version, deploy, and access the jar containing the
appropriate set of rules.
We do not want to embed the rules inside the project(s) that will be
using
the rules.
we want these rules to be common (as sun_checks). 

Therefore, once the rules'jar is available in the repository, it can be
accessed by maven (no probs)
BUT how can you make it available to eclipse at the same time ? (do you
explode the jar in the repository when you deploy it ?, so that eclipse
checkstyle can reference the xml files ...)

anyway, I posted the question in checkstyle mailing list.
If I get an answer, I'll post it

good day,

Christian-Luc



Greg_Vaughn wrote:
> 
>> I am using maven-checkstyle-plugin with a specific configuration file

>> (I made it as a resource in a jar and the plugin configuration works 
> fine:
>> checkstyle - or the plugin - is clever enough to get the xml file out
of 
> the
>> dependency jar)
>> 
>> I'd like to do the same within eclipse with the 
> eclipse-checkstyle-plugin
>> (so that checkstyle can be active during eclipse work, not just when
>> building with maven)
>> Unfortunately the checkstyle preference window does not seem to allow
a
>> reference to a jar.
>> it needs an xml file
>> This is not really a maven question but someone may know if my
request 
> is
>> possible ???
> 
> We did this last year, but the details aren't fresh on my mind. Let me

> know
> if this general approach is not enough.
> 
> We attached the checkstyle xml file to the project so it was deployed 
> along
> with the jar file to our corporate maven repository. Since that
repository
> is available via http, we configured the eclipse plugin to use that
url.
> 
> Now we have one mavenized project to manage the checkstyle rules. When
we
> deploy it, the checkstyle rules become available to both maven and
eclipse
> at the same time.
> 
> -Greg Vaughn
> 
> 
> ==
> 
> Confidentiality Notice: The information contained in and transmitted
with
> this communication is strictly confidential, is intended only for the
use
> of the intended recipient, and is the property of Countrywide
Financial
> Corporation or its affiliates and subsidiaries. If you are not the
> intended recipient, you are hereby notified that any use of the
> information contained in or transmitted with the communication or
> dissemination, distribution, or copying of this communication is
strictly
> prohibited by law. If you have received this communication in error,
> please immediately return this communication to the sender and delete
the
> original message and any copy of it in your possession.
> 
> ==
> 
> 
> 

-- 
View this message in context:
http://www.nabble.com/checkstyle-plugins%3A-maven-and-eclipse-tf4562913s
177.html#a13034381
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Deploying same version overwrites existing release

[Hayes, Peter]

Thanks, I'll look into that.

Peter 

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 26, 2007 12:37 PM
To: Maven Users List
Subject: Re: Deploying same version overwrites existing release

Not ideal, but you could set up a cron job or similar to frequently
set -w to all the files in your deploy directories. Then you couldn't
overwrite things due to filesystem privileges.

Wayne

On 9/26/07, Hayes, Peter <[EMAIL PROTECTED]> wrote:
> Yes that is true.  We are using clearcase though and the release
plugin
> has some limitations with regards to clearcase.
>
> I thought though that once a release is made, it should never be
changed
> as it is in the "wild" and may have already been used.  For instance,
I
> think recently the maven developers had a problem with the release of
> the archetype plugin and they did not just re-release that version,
they
> moved to a new one.  If this is the recommended process, then I would
> think it would be appropriate for the deploy command to (at least by
> default) not allow the overwriting of an existing artifact.
>
> Pete
>
> -Original Message-
> From: John Coleman [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 26, 2007 10:46 AM
> To: Maven Users List
> Subject: RE: Deploying same version overwrites existing release
>
> But if you use relase:prepare/release:perform then your snapshot
version
> number goes up afterwards and overwritting is impossible?
>
> John
>
> -Original Message-
> From: Hayes, Peter [mailto:[EMAIL PROTECTED]
> Sent: 26 September 2007 15:39
> To: Maven Users List
> Subject: Deploying same version overwrites existing release
>
> Is there a way to configure maven to not allow it to deploy over an
> existing release artifact?
>
> Peter Hayes
> Architecture & Shared Technology Services | Fidelity Investments
> Management Technology
>
>
> Eurobase International Limited and its subsidiaries (Eurobase) are
> unable to exercise control over the content of information in E-Mails.
> Any views and opinions expressed may be personal to the sender and are
> not necessarily those of Eurobase. Eurobase will not enter into any
> contractual obligations in respect of any part of its business in any
> E-mail.
>
> Privileged / confidential information may be contained in this message
> and /or any attachments. This E-mail is intended for the use of the
> addressee(s) only and may contain confidential information. If you are
> not the / an intended recipient, you are hereby notified that any use
or
> dissemination of this communication is strictly prohibited.  If you
> receive this transmission in error, please notify us immediately, and
> then delete this E-mail.
>
> Neither the sender nor Eurobase accepts any liability whatsoever for
any
> defects of any kind either in or arising from this E-mail
transmission.
> E-Mail transmission cannot be guaranteed to be secure or error-free,
as
> messages can be intercepted, lost, corrupted, destroyed, contain
> viruses, or arrive late or incomplete. Eurobase does not accept any
> responsibility for viruses and it is your responsibility to scan any
> attachments.
>
> Eurobase Systems Limited is the main trading company in the Eurobase
> International Group; registered in England and Wales as company number
> 02251162; registered address: Essex House, 2 County Place, Chelmsford,
> Essex CM2 0RE, UK.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Deploying same version overwrites existing release

[Hayes, Peter]

Yes that is true.  We are using clearcase though and the release plugin
has some limitations with regards to clearcase.  

I thought though that once a release is made, it should never be changed
as it is in the "wild" and may have already been used.  For instance, I
think recently the maven developers had a problem with the release of
the archetype plugin and they did not just re-release that version, they
moved to a new one.  If this is the recommended process, then I would
think it would be appropriate for the deploy command to (at least by
default) not allow the overwriting of an existing artifact.

Pete  

-Original Message-
From: John Coleman [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 26, 2007 10:46 AM
To: Maven Users List
Subject: RE: Deploying same version overwrites existing release

But if you use relase:prepare/release:perform then your snapshot version
number goes up afterwards and overwritting is impossible?

John

-Original Message-----
From: Hayes, Peter [mailto:[EMAIL PROTECTED] 
Sent: 26 September 2007 15:39
To: Maven Users List
Subject: Deploying same version overwrites existing release

Is there a way to configure maven to not allow it to deploy over an
existing release artifact?

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology


Eurobase International Limited and its subsidiaries (Eurobase) are
unable to exercise control over the content of information in E-Mails.
Any views and opinions expressed may be personal to the sender and are
not necessarily those of Eurobase. Eurobase will not enter into any
contractual obligations in respect of any part of its business in any
E-mail. 

Privileged / confidential information may be contained in this message
and /or any attachments. This E-mail is intended for the use of the
addressee(s) only and may contain confidential information. If you are
not the / an intended recipient, you are hereby notified that any use or
dissemination of this communication is strictly prohibited.  If you
receive this transmission in error, please notify us immediately, and
then delete this E-mail. 

Neither the sender nor Eurobase accepts any liability whatsoever for any
defects of any kind either in or arising from this E-mail transmission.
E-Mail transmission cannot be guaranteed to be secure or error-free, as
messages can be intercepted, lost, corrupted, destroyed, contain
viruses, or arrive late or incomplete. Eurobase does not accept any
responsibility for viruses and it is your responsibility to scan any
attachments.

Eurobase Systems Limited is the main trading company in the Eurobase
International Group; registered in England and Wales as company number
02251162; registered address: Essex House, 2 County Place, Chelmsford,
Essex CM2 0RE, UK.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Deploying same version overwrites existing release

[Hayes, Peter]

Is there a way to configure maven to not allow it to deploy over an
existing release artifact?

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology

RE: Eclipse and Maven "best practice"

[Hayes, Peter]

http://maven.apache.org/plugins/maven-eclipse-plugin/overview.html
http://m2eclipse.codehaus.org/
http://code.google.com/p/q4e/ 

-Original Message-
From: zm [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 13, 2007 10:54 AM
To: users@maven.apache.org
Subject: Eclipse and Maven "best practice"


Hi,

Can anyone help me with the best way to setup a Maven/Eclipse
environment? I
know there is a goal to produce an eclipse project with the pom, but I'm
trying to understand how to create one at hand, customise and include
it's
dependencies.

I have created 2 projects, "appTest" and "appCommon". The main project
is
"appTest" that depends on "appCommon".

The source directories are the default Maven (src/main/java) and that
directory is configured as "source" in eclipse, so it can compile the
code.

Then I've configured a specific directory "build" (same level as the
"src"
above), that eclipse will use to put the compiled classes (this folder
will
be ignored for SVN/CVS integration).

Everything looks great, and works nicelly. Or so it seems ...

No let's say I put a dependency on version Log4J 1.0. I make some code
accessing it, then eclipse will just mark it as invalid, since the Log4J
is
not in it's classpath. Maven, on the other end, downloads it from
central
repository and compiles successfully.

Now what would be the best way to put it to compile in eclipse?

The way I see it, I can include it in the project's classpath, and point
it
to the local repository jar that maven just downloaded.

Would this be the best option?
-- 
View this message in context:
http://www.nabble.com/Eclipse-and-Maven-%22best-practice%22-tf4436040s17
7.html#a12655883
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Re: Maven plugin for Eclipse

[Hayes, Peter]

http://code.google.com/p/q4e/wiki/Installation 

-Original Message-
From: Eric Wood [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 11, 2007 8:01 AM
To: Maven Users List
Subject: RE: Re: Maven plugin for Eclipse

How do you download the Q4E plug-in? The link below says that no download are 
avilable.

Eric 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sanchez
Sent: Monday, September 10, 2007 1:15 PM
To: Maven Users List
Subject: Re: Re: Maven plugin for Eclipse

it's a known issue with m2eclipse 0.0.10
http://jira.codehaus.org/browse/MNGECLIPSE-265

There's another Eclipse plugin Q4E http://code.google.com/p/q4e/ that me and 
other maven users are working on and doesn't have that bug.
Feel free to check it out.


On 9/10/07, De Vleeschauwer Nele <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Even when I use the Refresh Settings option, Eclipse still tries to connect 
> to the Internet Maven Repo instead of the mirror I defined in my maven 
> settings.xml file.
>
>
>
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Achim Abeling
> Sent: vrijdag 7 september 2007 8:41
> To: users@maven.apache.org
> Subject: Re: Maven plugin for Eclipse
>
> Hi,
>
> did you refresh the settings in eclipse?
> It has to be done under
> Window->Preferences->Maven->Refresh Settings.
>
> Best regards
> Achim
>
> De Vleeschauwer Nele wrote:
> > Hi,
> >
> > I have configured my settings.xml in this way and if I execute a maven 
> > command from a dos box, it is using our company's repository.
> > But if I call a maven command out of Eclipse, it goes directly to the Maven 
> > Repo site.
> >
> >
> >
> > -Original Message-
> > From: COPPENS, Fabien [mailto:[EMAIL PROTECTED]
> > Sent: donderdag 6 september 2007 14:14
> > To: Maven Users List
> > Subject: RE: Maven plugin for Eclipse
> >
> >
> >
> > I believe you can configure this in your maven settings.xml file via 
> > a profile :
> >
> > 
> >   
> >   MyDevRepo
> >   
> >   http://myrepository
> >   
> >   
> >   true
> >   
> >   
> >   false
> >   
> >   
> >   
> >   
> >
> >
> > -Message d'origine-
> > De : De Vleeschauwer Nele [mailto:[EMAIL PROTECTED]
> > Envoyé : jeudi 6 septembre 2007 14:11 À : Maven Users List Objet : 
> > Maven plugin for Eclipse
> >
> > Hi,
> >
> > For the moment I'm using version 3.3 of Eclipse with the Maven plugin 
> > installed.
> >
> > Each time when I execute a maven command in Eclipse, Eclipse tries to 
> > download the necessary artiftacts from the Maven Repo site 
> > (repo1.maven.org).
> > How can I configure that Eclipse should use the company's central Maven 
> > Repository to download new artifacts instead of the one on the Maven site ?
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> Visit our website! http://www.nbb.be
>
> "DISCLAIMER: The content of this e-mail message should not be 
> construed as binding on the part of the National Bank of Belgium
> (NBB) unless otherwise and previously stated. The opinions expressed 
> in this message are solely those of the author and do not necessarily 
> reflect NBB viewpoints, particularly when the content of this message, 
> or part thereof, is private by nature or does not fall within the 
> professional scope of its author."
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
 -- The Princess Bride

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Feature branches and merging

[Hayes, Peter]

I'd like to get some feedback on best practices of developing with
Maven.

Suppose we have a 1.0-SNAPSHOT mainline development version of a
multi-module maven project.  We would like to create a feature branch
off the mainline dev branch.  When developing on the feature branch I
would think we would need to change the version of all modules to
something like 1.0-wizzbang-SNAPSHOT.  Is that the recommended approach?
Is there an automated manner of changing all poms' versions in a single
command?  I know the release plugin does something like this but I don't
think it is exactly intended for this.

Finally, when merging the feature branch back to the mainline branch, we
would not want to merge the version fields in the POM as those would
only be appropriate on the feature branch.  We use clearcase, but is
this normally a difficult problem in code repositories?  Is there a way
to mark the version tag as non-mergable?

Thanks,

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology

Enable file protocol for adding Maven 2.0.x projects in 1.1-alpha-2

[Hayes, Peter]

In 1.0.3, there was a section in apps\continuum\conf\application.xml to
allow the file protocol to add a project to continuum.  How do I go
about enabling this in 1.1-alpha-2?

Thanks,

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology

RE: M2 Eclipse project dependency

[Hayes, Peter]

Two ways :

Maven Plugin for Eclipse

Use the maven plugin for eclipse
(http://maven.apache.org/plugins/maven-eclipse-plugin/index.html), i.e.
mvn eclipse:eclipse.  This will generate (modify if already existing) a
.project and a .classpath file for your eclipse project or if you have a
multi-module build, it will repeat this process for each module.  The
key piece that you are looking for is that for multi-module projects, it
will create an eclipse project reference in the generated .classpath
file.

Eclipse Plugin for Maven

The m2eclipse plugin (http://m2eclipse.codehaus.org/) which is what you
are using is a dynamic classpath manager in that it reads your pom.xml
files for your projects and manages an eclipse classpath container which
reflects your maven dependencies.  As of version 0.0.10, the plugin will
automatically reference other projects in your eclipse workspace if
those projects (groupId, artifactId & versionId) are the same as one of
your dependencies.  This is a really nice feature though I have found
the plugin to be somewhat unstable when changing dependencies and / or
using inherited dependency management versioning.  

For our projects, we have been using the Maven Plugin for Eclipse as it
"just works" though I am waiting to move to the m2eclipse plugin once it
improves stability and "just works" as its dynamic nature promises
easier use.

-Original Message-
From: Robert Blixt [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 30, 2007 4:42 AM
To: users@maven.apache.org
Subject: M2 Eclipse project dependency


  Hi,

I'm trying to get a handle on Maven2 (Been using Ant
for a while, and this seems to be the next logical step).

However, I've stumpled upon some problems. I have two
projects (Project A and B). Project A is dependent on
project B. (I'm using Eclipse IDE with Maven plugin).

I know how to create a jar of project B and make a dependency
of that in project A. But I would like to make a dependency
directly to the Eclipse project. So I do not need to create
a jar each time I've updated project B. Is this possible?

What is the preferred way to deal with this?

Kind Regards,
Robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Clearcase history shows limited information in build results

[Hayes, Peter]

History on the build result only shows file modified, but not the
revision number, comment and who changed it.  I think the problem might
be that the call to get history is executed from the top directory
 and not the subdirectory that contains the pom.xml.

Does anyone else see this problem?

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology

RE: How to NOT include test resources in jar

[Hayes, Peter]

Just a shot in the dark but did you try an "mvn clean package"?  Maybe the test 
resources had at some point made it into the target\classes directory...

Pete 

-Original Message-
From: Eric Daigneault [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 10, 2007 11:32 AM
To: Maven Users List
Subject: How to NOT include test resources in jar

Hi everybody,

I'm trying to package my projects and everything works fine except that 
test resources are systematically included in the jar.  No matter where 
I put them or what I declare in testResources they always end up in the 
jar.  This can me problematic as some of the test can be very extensive 
as they can include test databases of very big test files.  Since their 
only uses is for unit and specification testing there is absolutely no 
reason to include them in the final release.


The project is arranged as follows :

com.mypackage.pack.specific/
|
\-src
|--main
|  \-java
|  \-- My source tree
\--test
 \--java
   |-- My test source tree
   \--resources
   |--unitTest
   \--SpecTest

My problem is that the source tree from src/test is not included in the 
jar...  actually this is fine but the content of resources is included 
at the root of the jar..

The end result in the jar is the following :

specific-1.0.jar
|--META-INF
|\--  ... pom and properties
|--com.mypackage.pack
|   \--My source tree compiled
|--unitTest   <-- Why is this here ???
\--SpecTest <--Why is this here too ???  want them removed

here is the effective POM from my latest attempt :



  
base
com.mypackage
1.0
  
  4.0.0
  com.mypackage.pack
  specific
  specific
  1.0
  http://maven.apache.org
  2007
  

  eric
  myself
 
  
  

D:\workspace\com.mypackage.pack.specific\src\main\java
src/main/scripts

D:\workspace\com.mypackage.pack.specific\src\test\java

D:\workspace\com.mypackage.pack.specific\target\classes

D:\workspace\com.mypackage.pack.specific\target\test-classes

  

D:\workspace\com.mypackage.pack.specific\src\main\config
  


  
/src/test/java/resources
  

D:\workspace\com.mypackage.pack.specific\target
specific-1.0

  
maven-compiler-plugin

  1.6
  1.6

  
  
maven-help-plugin
2.0.1
  

  
  
 
  
false
  
  central
  Maven Repository Switchboard
  http://repo1.maven.org/maven2

  
  

  
never
  
  
false
  
  central
  Maven Plugin Repository
  http://repo1.maven.org/maven2

  
  

  junit
  junit
  4.1
  test


  com.mypackage
  pack
  1.0

  
  
target/site
  
 

Thanks,

Éric

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Maven2 plugin for eclipse : OK now

[Hayes, Peter]

In this case, it is not the JDK configured within Eclipse itself (this 
configures the JDK's available to compile with), but the JDK that Eclipse is 
run with externally.  Check your environment variables for JAVA_HOME and your 
path for the version of Java that you use.  In my case I have (for Windows) :

MAVEN_HOME = c:\dev\tools\maven-2.0.5
JAVA_HOME = c:\Program Files\Java\jdk1.5.0_10
PATH = %MAVEN_HOME%\bin;%JAVA_HOME%\bin

This means that when eclipse is invoked (or Maven) it uses the JDK1.5.0_10 to 
run.  

HTH,

Pete

-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 13, 2007 8:49 AM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse : OK now

At the begining in InstalledJRE it was : c:\eclipse.
I modified it to C:\j2sdk1.4.2_13. but still the same error.

So I must run eclipse with -Djava.home or what 

thx

-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 13 mars 2007 12:36
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now

This actually should work in the 0.0.10 version of the m2eclipse plugin.  Make 
sure that you are using a _JDK_ and not a JRE to run Eclipse / Maven.  The 
tools.jar is not present in the JRE package. 

-Original Message-
From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 13, 2007 8:31 AM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse : OK now

Hi,

It is possible that dependencies with "system" scope are not correctly
handled by the plugin. Check that tools.jar appears in the list of jars
within the "Maven Dependencies" library container. If it is not there,
just add it manually to the Eclipse project classpath.

Hope this helps you,
Rodrigo

Marouane Amraoui wrote:
>
> The missing file jar is com.sun.tools . is a dependency of commons-
>
> attributs-compiler. In the pom file of commons-attributs-compiler :
>
>  com.sun
>   tools
>   1.4.2
>   system
>   ${java.home}/../lib/tools.jar
>  
>
> I didn't undrestand what i need to do in this case 
>
>
>
>
>
> -Message d'origine-
> De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 13 mars 2007 11:11
> À : Maven Users List
> Objet : RE: Maven2 plugin for eclipse : OK now
>
>
> Is OK  now :). So i noticed that in the pom file signal an error of a
> messing jar .  for that the container doesn't work I think.
>
> Thx a lot for your help.
>
>
> -Message d'origine-
> De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 13 mars 2007 10:56
> À : Maven Users List
> Objet : RE: Maven2 plugin for eclipse
>
>
> I enabled the maven project , but still have error compilation  due of the
> dependency 
>
>
> I have this classpath :
>
> .classpath
> 
>
> 
> 
>   
>path="src/test"/>
>path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
>   
> 
>
> .project
> 
> 
> 
>   framework
>   
>   
>   
>   
>   
>   org.eclipse.jdt.core.javabuilder
>   
>   
>   
>   
>   org.maven.ide.eclipse.maven2Builder
>   
>   
>   
>   
>   
>   org.eclipse.jdt.core.javanature
>   org.maven.ide.eclipse.maven2Nature
>   
> 
>
>
>
> -Message d'origine-
> De : Hayes, Peter [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 12 mars 2007 19:39
> À : Maven Users List
> Objet : RE: Maven2 plugin for eclipse
>
> Yes, you will not have to manage the .classpath manually.  Make sure to
> remove any entries defined in there that are now redundant based on the
> m2eclipse plugin's classpath management.
>
> I generally have the following in my .classpath files :
>
> 
> 
>   
>   
>   
>   
>path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
>   
> 
>
> Pete
>
> -Original Message-
> From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 12, 2007 3:31 PM
> To: Maven Users List
> Subject: RE: Maven2 plugin for eclipse
>
> I didn't have enabled my project maven . so If I enable it we don't need
> to execute eclipse:eclipse inorder to synchronize the pom dependency and
> .classpth

RE: Maven2 plugin for eclipse : OK now

[Hayes, Peter]

This actually should work in the 0.0.10 version of the m2eclipse plugin.  Make 
sure that you are using a _JDK_ and not a JRE to run Eclipse / Maven.  The 
tools.jar is not present in the JRE package. 

-Original Message-
From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 13, 2007 8:31 AM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse : OK now

Hi,

It is possible that dependencies with "system" scope are not correctly
handled by the plugin. Check that tools.jar appears in the list of jars
within the "Maven Dependencies" library container. If it is not there,
just add it manually to the Eclipse project classpath.

Hope this helps you,
Rodrigo

Marouane Amraoui wrote:
>
> The missing file jar is com.sun.tools . is a dependency of commons-
>
> attributs-compiler. In the pom file of commons-attributs-compiler :
>
>  com.sun
>   tools
>   1.4.2
>   system
>   ${java.home}/../lib/tools.jar
>  
>
> I didn't undrestand what i need to do in this case 
>
>
>
>
>
> -Message d'origine-
> De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 13 mars 2007 11:11
> À : Maven Users List
> Objet : RE: Maven2 plugin for eclipse : OK now
>
>
> Is OK  now :). So i noticed that in the pom file signal an error of a
> messing jar .  for that the container doesn't work I think.
>
> Thx a lot for your help.
>
>
> -Message d'origine-
> De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 13 mars 2007 10:56
> À : Maven Users List
> Objet : RE: Maven2 plugin for eclipse
>
>
> I enabled the maven project , but still have error compilation  due of the
> dependency 
>
>
> I have this classpath :
>
> .classpath
> 
>
> 
> 
>   
>path="src/test"/>
>path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
>   
> 
>
> .project
> 
> 
> 
>   framework
>   
>   
>   
>   
>   
>   org.eclipse.jdt.core.javabuilder
>   
>   
>   
>   
>       org.maven.ide.eclipse.maven2Builder
>   
>   
>   
>   
>   
>   org.eclipse.jdt.core.javanature
>   org.maven.ide.eclipse.maven2Nature
>   
> 
>
>
>
> -Message d'origine-
> De : Hayes, Peter [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 12 mars 2007 19:39
> À : Maven Users List
> Objet : RE: Maven2 plugin for eclipse
>
> Yes, you will not have to manage the .classpath manually.  Make sure to
> remove any entries defined in there that are now redundant based on the
> m2eclipse plugin's classpath management.
>
> I generally have the following in my .classpath files :
>
> 
> 
>   
>   
>   
>   
>path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
>   
> 
>
> Pete
>
> -Original Message-
> From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 12, 2007 3:31 PM
> To: Maven Users List
> Subject: RE: Maven2 plugin for eclipse
>
> I didn't have enabled my project maven . so If I enable it we don't need
> to execute eclipse:eclipse inorder to synchronize the pom dependency and
> .classpth 
>
> -Message d'origine-
> De : Hayes, Peter [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 12 mars 2007 19:22
> À : Maven Users List
> Objet : RE: Maven2 plugin for eclipse
>
> Sorry, make sure that you enable the plugin on your project.  You have to
> right-click the project and there should be a Maven2 menu.  Select enable.
>
> Pete
>
> -Original Message-
> From: Hayes, Peter
> Sent: Monday, March 12, 2007 3:20 PM
> To: Maven Users List
> Subject: RE: Maven2 plugin for eclipse
>
>
> http://m2eclipse.codehaus.org/
>
> This plugin keeps your classpath in synch with your pom file via an
> Eclipse classpath container.  It's very good.
>
> -Original Message-
> From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 12, 2007 2:05 PM
> To: Maven Users List
> Subject: Maven2 plugin for eclipse
>
> I m using Maven2 plugin for eclipse .
>
> Version plugin is : 0.0.10.
>
>
>
> I created a maven project . I added

RE: Maven2 plugin for eclipse

[Hayes, Peter]

Yes, you will not have to manage the .classpath manually.  Make sure to remove 
any entries defined in there that are now redundant based on the m2eclipse 
plugin's classpath management. 

I generally have the following in my .classpath files :












Pete

-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 12, 2007 3:31 PM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse

I didn't have enabled my project maven . so If I enable it we don't need to 
execute eclipse:eclipse inorder to synchronize the pom dependency and .classpth 


-Message d'origine-----
De : Hayes, Peter [mailto:[EMAIL PROTECTED] 
Envoyé : lundi 12 mars 2007 19:22
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse

Sorry, make sure that you enable the plugin on your project.  You have to 
right-click the project and there should be a Maven2 menu.  Select enable.

Pete 

-Original Message-
From: Hayes, Peter 
Sent: Monday, March 12, 2007 3:20 PM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse


http://m2eclipse.codehaus.org/ 

This plugin keeps your classpath in synch with your pom file via an Eclipse 
classpath container.  It's very good.

-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 12, 2007 2:05 PM
To: Maven Users List
Subject: Maven2 plugin for eclipse

I m using Maven2 plugin for eclipse . 

Version plugin is : 0.0.10.

 

I created a maven project . I added dependency using the plugin.

 

when I add the dependency it only added in pom file and note in eclipse file 
.classpath   this obligate me to do 

A double  work 

 

There is a solution for that ???

 

---

Merouane AMRAOUI
Consultant Expert
Division Développement
Email.: [EMAIL PROTECTED]

Gsm  .: 065 19 60 99   
Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70
OMNIDATA , 74 Bv AbdelMoumen

 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Maven2 plugin for eclipse

[Hayes, Peter]

Sorry, make sure that you enable the plugin on your project.  You have to 
right-click the project and there should be a Maven2 menu.  Select enable.

Pete 

-Original Message-
From: Hayes, Peter 
Sent: Monday, March 12, 2007 3:20 PM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse


http://m2eclipse.codehaus.org/ 

This plugin keeps your classpath in synch with your pom file via an Eclipse 
classpath container.  It's very good.

-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 12, 2007 2:05 PM
To: Maven Users List
Subject: Maven2 plugin for eclipse

I m using Maven2 plugin for eclipse . 

Version plugin is : 0.0.10.

 

I created a maven project . I added dependency using the plugin.

 

when I add the dependency it only added in pom file and note in eclipse file 
.classpath   this obligate me to do 

A double  work 

 

There is a solution for that ???

 

---

Merouane AMRAOUI
Consultant Expert
Division Développement
Email.: [EMAIL PROTECTED]

Gsm  .: 065 19 60 99   
Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70
OMNIDATA , 74 Bv AbdelMoumen

 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Maven2 plugin for eclipse

[Hayes, Peter]

http://m2eclipse.codehaus.org/ 

This plugin keeps your classpath in synch with your pom file via an Eclipse 
classpath container.  It's very good.

-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 12, 2007 2:05 PM
To: Maven Users List
Subject: Maven2 plugin for eclipse

I m using Maven2 plugin for eclipse . 

Version plugin is : 0.0.10.

 

I created a maven project . I added dependency using the plugin.

 

when I add the dependency it only added in pom file and note in eclipse file 
.classpath   this obligate me to do 

A double  work 

 

There is a solution for that ???

 

---

Merouane AMRAOUI
Consultant Expert
Division Développement
Email.: [EMAIL PROTECTED]

Gsm  .: 065 19 60 99   
Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70
OMNIDATA , 74 Bv AbdelMoumen

 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Installing 3rd party jar to remote repository with sources jar

[Hayes, Peter]

Is it possible to use the deploy:deploy-file target to deploy a 3rd
party jar into a remote repostory while including an attached sources
jar?  I don't see any parameters on
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.htm
l that would indicate that this is possible.

Peter Hayes
Architecture & Shared Technology Services | Fidelity Investments
Management Technology

RE: How to read this time stamp in snapshot ?

[Hayes, Peter]

I believe it is in GMT time so that there is no conflict in finding the
latest snapshot regardless of your localization settings.  I don't know
if there is a way to configure it, but you probably don't want to do so
anyways.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 25, 2007 11:01 AM
To: 'Maven Users List'
Subject: How to read this time stamp in snapshot ?

Hi All,

I built some snapshot version of project on 24th Jan.2007 morning 10 am
at 
my local time, but what i see in my maven-metadata.xml is

20070124.212320


Date part is ok in this, but what is the time part in this ???  is there

some thing i need to configure to get right time there??


Thanks,
Raghurajan Gurunathan



-
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law.  If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED.  Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]