Re: Add third party jars from the file system to final executable jar without adding the third party jars in local maven repo

[Stephen Connolly]

The new link is
https://www.cloudbees.com/blog/playing-trade-offs-maven *BUT* somebody
managed to completely screw up the XML formatting when migrating from
the old blog hosting to the new blog hosting...

On 26 October 2015 at 17:21, Curtis Rueden  wrote:
> Hi Reena,
>
> Stephen Connelly wrote a great blog post a couple of years ago addressing
> similar use cases. The URL is/was:
>
> http://developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html
>
> Unfortunately, it seems the CloudBees Developer Blog is currently not
> working (it redirects to the main CloudBees page). But you can use Google's
> cache to read it:
>
> http://webcache.googleusercontent.com/search?q=cache:g6o4OFBnC9wJ:developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html+=1=en=clnk=us
>
> HTH,
> Curtis
>
> On Mon, Oct 26, 2015 at 11:50 AM, Wayne Fay  wrote:
>
>> Sounds like you know the answer. Use the "mvn install" file command.
>>
>> Wayne
>>
>> On Mon, Oct 26, 2015 at 9:53 AM, reena upadhyay 
>> wrote:
>> > Can you please provide some code snippet, how to add it to local repo
>> > through pom.xml. I don't want it add to my local maven repo using mvn
>> > install file command.
>> >
>> > On Mon, Oct 26, 2015 at 8:21 PM, Anders Hammar 
>> wrote:
>> >
>> >> The system scope is deprecated and the issues you're running into is
>> likely
>> >> due to that. The solution is to add the library to your internal
>> (remote)
>> >> repo or at least your local repo.
>> >>
>> >> /Anders
>> >>
>> >> On Mon, Oct 26, 2015 at 3:26 PM, reena upadhyay 
>> >> wrote:
>> >>
>> >> > I want dependencies that are having system scope to be part of my
>> project
>> >> > final executable jar. I tried maven-assembly, maven-shade and
>> >> > maven-dependency plugin. But using these plugins, only those
>> dependency
>> >> of
>> >> > my project which were present in my local maven repository were
>> getting
>> >> > added. Dependency with system scope (not present in my local maven
>> repo)
>> >> > are not getting added in the final executable jar.
>> >> >
>> >> > I tried searching over google, but most of the links are suggesting to
>> >> add
>> >> > it local maven repo first. I have some limitations so I cannot add
>> those
>> >> > dependency on local repo. I want it to picked from file system
>> directly,
>> >> > and wanted it to be part of final executable jar.
>> >> >
>> >> > 
>> >> > 
>> >> > org.teradata
>> >> > teradata
>> >> > 4.0
>> >> > system
>> >> >
>> >> >
>> >>
>> ${basedir}/../../../lib/terajdbc4.jar
>> >> >
>> >> > Above dependency is not getting added in the final jar that maven is
>> >> > building.
>> >> >
>> >> > Please suggest me the right plugin with its usage for this use case.
>> >> >
>> >> > Any help on this would be really appreciated.
>> >> >
>> >>
>>
>> -
>> 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: Add third party jars from the file system to final executable jar without adding the third party jars in local maven repo

[Anders Hammar]

Sorry, I don't have such a solution handy as it's not anything that is
adviced from a Maven perspective. However, most likely Google is your
friend here and could find some solution.
The "Maven way" is to add the library to your internal (remote) repo so
that you can declare a dependency that will work for all your team mates
without any additional magic.

/Anders

On Mon, Oct 26, 2015 at 3:53 PM, reena upadhyay  wrote:

> Can you please provide some code snippet, how to add it to local repo
> through pom.xml. I don't want it add to my local maven repo using mvn
> install file command.
>
> On Mon, Oct 26, 2015 at 8:21 PM, Anders Hammar  wrote:
>
> > The system scope is deprecated and the issues you're running into is
> likely
> > due to that. The solution is to add the library to your internal (remote)
> > repo or at least your local repo.
> >
> > /Anders
> >
> > On Mon, Oct 26, 2015 at 3:26 PM, reena upadhyay 
> > wrote:
> >
> > > I want dependencies that are having system scope to be part of my
> project
> > > final executable jar. I tried maven-assembly, maven-shade and
> > > maven-dependency plugin. But using these plugins, only those dependency
> > of
> > > my project which were present in my local maven repository were getting
> > > added. Dependency with system scope (not present in my local maven
> repo)
> > > are not getting added in the final executable jar.
> > >
> > > I tried searching over google, but most of the links are suggesting to
> > add
> > > it local maven repo first. I have some limitations so I cannot add
> those
> > > dependency on local repo. I want it to picked from file system
> directly,
> > > and wanted it to be part of final executable jar.
> > >
> > > 
> > > 
> > > org.teradata
> > > teradata
> > > 4.0
> > > system
> > >
> > >
> >
> ${basedir}/../../../lib/terajdbc4.jar
> > >
> > > Above dependency is not getting added in the final jar that maven is
> > > building.
> > >
> > > Please suggest me the right plugin with its usage for this use case.
> > >
> > > Any help on this would be really appreciated.
> > >
> >
>

Re: Add third party jars from the file system to final executable jar without adding the third party jars in local maven repo

[reena upadhyay]

Can you please provide some code snippet, how to add it to local repo
through pom.xml. I don't want it add to my local maven repo using mvn
install file command.

On Mon, Oct 26, 2015 at 8:21 PM, Anders Hammar  wrote:

> The system scope is deprecated and the issues you're running into is likely
> due to that. The solution is to add the library to your internal (remote)
> repo or at least your local repo.
>
> /Anders
>
> On Mon, Oct 26, 2015 at 3:26 PM, reena upadhyay 
> wrote:
>
> > I want dependencies that are having system scope to be part of my project
> > final executable jar. I tried maven-assembly, maven-shade and
> > maven-dependency plugin. But using these plugins, only those dependency
> of
> > my project which were present in my local maven repository were getting
> > added. Dependency with system scope (not present in my local maven repo)
> > are not getting added in the final executable jar.
> >
> > I tried searching over google, but most of the links are suggesting to
> add
> > it local maven repo first. I have some limitations so I cannot add those
> > dependency on local repo. I want it to picked from file system directly,
> > and wanted it to be part of final executable jar.
> >
> > 
> > 
> > org.teradata
> > teradata
> > 4.0
> > system
> >
> >
> ${basedir}/../../../lib/terajdbc4.jar
> >
> > Above dependency is not getting added in the final jar that maven is
> > building.
> >
> > Please suggest me the right plugin with its usage for this use case.
> >
> > Any help on this would be really appreciated.
> >
>

Re: Add third party jars from the file system to final executable jar without adding the third party jars in local maven repo

[Anders Hammar]

The system scope is deprecated and the issues you're running into is likely
due to that. The solution is to add the library to your internal (remote)
repo or at least your local repo.

/Anders

On Mon, Oct 26, 2015 at 3:26 PM, reena upadhyay  wrote:

> I want dependencies that are having system scope to be part of my project
> final executable jar. I tried maven-assembly, maven-shade and
> maven-dependency plugin. But using these plugins, only those dependency of
> my project which were present in my local maven repository were getting
> added. Dependency with system scope (not present in my local maven repo)
> are not getting added in the final executable jar.
>
> I tried searching over google, but most of the links are suggesting to add
> it local maven repo first. I have some limitations so I cannot add those
> dependency on local repo. I want it to picked from file system directly,
> and wanted it to be part of final executable jar.
>
> 
> 
> org.teradata
> teradata
> 4.0
> system
>
> ${basedir}/../../../lib/terajdbc4.jar
>
> Above dependency is not getting added in the final jar that maven is
> building.
>
> Please suggest me the right plugin with its usage for this use case.
>
> Any help on this would be really appreciated.
>

Add third party jars from the file system to final executable jar without adding the third party jars in local maven repo

[reena upadhyay]

I want dependencies that are having system scope to be part of my project
final executable jar. I tried maven-assembly, maven-shade and
maven-dependency plugin. But using these plugins, only those dependency of
my project which were present in my local maven repository were getting
added. Dependency with system scope (not present in my local maven repo)
are not getting added in the final executable jar.

I tried searching over google, but most of the links are suggesting to add
it local maven repo first. I have some limitations so I cannot add those
dependency on local repo. I want it to picked from file system directly,
and wanted it to be part of final executable jar.



org.teradata
teradata
4.0
system
${basedir}/../../../lib/terajdbc4.jar

Above dependency is not getting added in the final jar that maven is
building.

Please suggest me the right plugin with its usage for this use case.

Any help on this would be really appreciated.

Re: Add third party jars from the file system to final executable jar without adding the third party jars in local maven repo

[Curtis Rueden]

Hi Reena,

Stephen Connelly wrote a great blog post a couple of years ago addressing
similar use cases. The URL is/was:

http://developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html

Unfortunately, it seems the CloudBees Developer Blog is currently not
working (it redirects to the main CloudBees page). But you can use Google's
cache to read it:

http://webcache.googleusercontent.com/search?q=cache:g6o4OFBnC9wJ:developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html+=1=en=clnk=us

HTH,
Curtis

On Mon, Oct 26, 2015 at 11:50 AM, Wayne Fay  wrote:

> Sounds like you know the answer. Use the "mvn install" file command.
>
> Wayne
>
> On Mon, Oct 26, 2015 at 9:53 AM, reena upadhyay 
> wrote:
> > Can you please provide some code snippet, how to add it to local repo
> > through pom.xml. I don't want it add to my local maven repo using mvn
> > install file command.
> >
> > On Mon, Oct 26, 2015 at 8:21 PM, Anders Hammar 
> wrote:
> >
> >> The system scope is deprecated and the issues you're running into is
> likely
> >> due to that. The solution is to add the library to your internal
> (remote)
> >> repo or at least your local repo.
> >>
> >> /Anders
> >>
> >> On Mon, Oct 26, 2015 at 3:26 PM, reena upadhyay 
> >> wrote:
> >>
> >> > I want dependencies that are having system scope to be part of my
> project
> >> > final executable jar. I tried maven-assembly, maven-shade and
> >> > maven-dependency plugin. But using these plugins, only those
> dependency
> >> of
> >> > my project which were present in my local maven repository were
> getting
> >> > added. Dependency with system scope (not present in my local maven
> repo)
> >> > are not getting added in the final executable jar.
> >> >
> >> > I tried searching over google, but most of the links are suggesting to
> >> add
> >> > it local maven repo first. I have some limitations so I cannot add
> those
> >> > dependency on local repo. I want it to picked from file system
> directly,
> >> > and wanted it to be part of final executable jar.
> >> >
> >> > 
> >> > 
> >> > org.teradata
> >> > teradata
> >> > 4.0
> >> > system
> >> >
> >> >
> >>
> ${basedir}/../../../lib/terajdbc4.jar
> >> >
> >> > Above dependency is not getting added in the final jar that maven is
> >> > building.
> >> >
> >> > Please suggest me the right plugin with its usage for this use case.
> >> >
> >> > Any help on this would be really appreciated.
> >> >
> >>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Add third party jars from the file system to final executable jar without adding the third party jars in local maven repo

[Wayne Fay]

Sounds like you know the answer. Use the "mvn install" file command.

Wayne

On Mon, Oct 26, 2015 at 9:53 AM, reena upadhyay  wrote:
> Can you please provide some code snippet, how to add it to local repo
> through pom.xml. I don't want it add to my local maven repo using mvn
> install file command.
>
> On Mon, Oct 26, 2015 at 8:21 PM, Anders Hammar  wrote:
>
>> The system scope is deprecated and the issues you're running into is likely
>> due to that. The solution is to add the library to your internal (remote)
>> repo or at least your local repo.
>>
>> /Anders
>>
>> On Mon, Oct 26, 2015 at 3:26 PM, reena upadhyay 
>> wrote:
>>
>> > I want dependencies that are having system scope to be part of my project
>> > final executable jar. I tried maven-assembly, maven-shade and
>> > maven-dependency plugin. But using these plugins, only those dependency
>> of
>> > my project which were present in my local maven repository were getting
>> > added. Dependency with system scope (not present in my local maven repo)
>> > are not getting added in the final executable jar.
>> >
>> > I tried searching over google, but most of the links are suggesting to
>> add
>> > it local maven repo first. I have some limitations so I cannot add those
>> > dependency on local repo. I want it to picked from file system directly,
>> > and wanted it to be part of final executable jar.
>> >
>> > 
>> > 
>> > org.teradata
>> > teradata
>> > 4.0
>> > system
>> >
>> >
>> ${basedir}/../../../lib/terajdbc4.jar
>> >
>> > Above dependency is not getting added in the final jar that maven is
>> > building.
>> >
>> > Please suggest me the right plugin with its usage for this use case.
>> >
>> > Any help on this would be really appreciated.
>> >
>>

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

Re: Third party jars

[John Stoneham]

On Wed, Dec 24, 2008 at 9:20 AM, Alex Athanasopoulos
alex.a.athens...@gmail.com wrote:
 Is there a way to convert a local repository into a remote repository, or
 should I upload each artifact to Nexus again? (I have a few dozen).

I understand that Nexus 1.2 features some command-line scripts to do
exactly this sort of thing, and an option to regenerate
maven-metadata.xml. But Nexus stores as flat files on disk, so you
ought to be able to instantiate your Nexus repository and copy
directly in.

I'd venture to say any further discussion ought to move to the
nexus-users list however.

- John

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

Re: Third party jars

[Brian Fox]

Yes we do have a tool for this

--Brian (mobile)


On Dec 24, 2008, at 3:55 PM, John Stoneham ly...@lyrically.net  
wrote:



On Wed, Dec 24, 2008 at 9:20 AM, Alex Athanasopoulos
alex.a.athens...@gmail.com wrote:
Is there a way to convert a local repository into a remote  
repository, or

should I upload each artifact to Nexus again? (I have a few dozen).


I understand that Nexus 1.2 features some command-line scripts to do
exactly this sort of thing, and an option to regenerate
maven-metadata.xml. But Nexus stores as flat files on disk, so you
ought to be able to instantiate your Nexus repository and copy
directly in.

I'd venture to say any further discussion ought to move to the
nexus-users list however.

- John

-
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: Third party jars

[Alex Athanasopoulos]

Thank you Brian,

I am now using Nexus Repository Manager, and it does save me from a lot of
hassle.  It was easier than I thought.  I just resisted at first, because
switching from Ant to Maven was more work than I thought it would be, so I
didn't want to get deeper into trouble with repository managers.

Is there a way to convert a local repository into a remote repository, or
should I upload each artifact to Nexus again? (I have a few dozen).

For now, I've copied my 3rd party section from my local repository directly
to the Nexus 3rd-party repo, and it seems to work.  I removed the metadata
files, since they are local repo metadata.  Of course, I'm now adding new
3rd party jars through Nexus.

I've found this related issue, but it doesn't explain the solution:

https://issues.sonatype.org/browse/NEXUS-996

-Alex

On Sat, Nov 29, 2008 at 8:27 PM, Brian Fox bri...@reply.infinity.nu wrote:

 You could save youself a lot of hassle with a repo manager. You shouldn't
 use local repos as remote repos because the metadata is different. Also with
 unmanaged repos, snapshot accumulation will become a problem.

 --Brian (mobile)

RE: Third party jars

[John.Baker]

Hi,

Thanks for the suggestion, but I was already aware of this and I was
wondering if there's an easier mechanism?   Such as mvn being smart with
the jar name and coming up with the group/artifact ID, but I suspect
that's beginning to ask too much!


John

 -Original Message-
 From: Stephen Connolly [mailto:[EMAIL PROTECTED] 
 Sent: 01 December 2008 08:49
 To: Maven Users List
 Subject: Re: Third party jars
 
 mvn deploy:deploy-file -DgroupId=foo -DartifactId=bar 
 -Dversion=1.0-foo -Dpackaging=jar -DgeneratePom=true 
 -Dfile=foo.jar ...
 
 And with newer versions of the maven-deploy-plugin, 
 generatePom defaults to true.
 
 It should be trivial for you to write a shell script or batch 
 file that loops through all the jar files in a directory and 
 just calls mvn to do the deploy for you.
 
 (BTW, the generated pom is a minimal pom, and does not 
 specify dependencies, but you just want to pull them all in, 
 so it will work for you and get you up and running)
 
 -Stephen
 
 2008/12/1 [EMAIL PROTECTED]
 
  Hi,
 
  Thanks for all the feedback.  I guess my reasoning was that 
 inventing 
  the meta data (group/artifactId/version) for 20 jars is a 
 little time 
  consuming - is there an easier way to do this?  I.e. Is 
 there a maven 
  command to take a directory full of jars and upload them 
 into my local 
  repository (~/.m2/repository) and generate a set of dependency 
  information for me?  Or even a pom with all the dependencies!
 
 
  John
 
   -Original Message-
   From: Alex Athanasopoulos [mailto:[EMAIL PROTECTED]
   Sent: 29 November 2008 10:34
   To: Maven Users List
   Subject: Re: Third party jars
  
   Why not put the jars in a repository?  A repository is 
 perfect for 
   containing 3rd party jars, and one of maven's major 
 benefits.  Once 
   you do that, you don't need to refer to the jars through 
 a hardcoded 
   path, but simply by a portable artifact identifier.  You 
 don't need 
   any special tools or repository managers, but you do need 
 to setup 
   your own remote repository somehow.
  
   I simply use mvn install:install-file, and then copy the 
 generated 
   files from my local repository to a remote repository that I have 
   created just for 3rd party libs.
  
   I'm fairly new to maven, and this is one of the first 
 things I had 
   to do.
The rest is just defining and managing repositories, 
 which can be a 
   discussion of its own.  I'm not using any repository managers yet 
   (learning to live with maven is enough work for me right 
 now).  My 
   A-B-Cs of repository management have been the following:
  
   A)  At first I used only my local repository, which I shared with 
   other developers by putting it under version control in svn, just 
   like I had my
   3rd party libs before maven.   I used mvn -o most of the
   time, to avoid
   accessing Maven's central repository.  I was a bit annoyed that I 
   had to use -o.  I tried to use the offline configuration in 
   settings.xml, but I couldn't get it to work (one of my first 
   frustrations with maven).  mvn -o worked reliably, but I had to 
   remember to use it.  Whenever I needed a piece of Maven that I 
   didn't have, I used mvn without the -o flag, and once everything 
   worked, I added the new artifacts from my local 
 repository to svn.  
   I did not add my snapshots.
  
   B)  I then figured out how to avoid the -o flag, by defining a 
   mirror of the central repository in my settings.xml.  The 
 mirror was 
   simply an http-accessible location of the single svn-managed 
   repository that I had.
Whenever I needed to use a new piece of maven, I 
 commented out the 
   mirror specifiction in my settings.xml, ran mvn so it 
 could get new 
   pieces from repo1.maven.org, and then took the comment out of 
   settings.xml.  The rest was as in A.
  
   C)  I now use two repositories:
   1)  A repository of non-maven released artifacts.
   Essentially this contains 3rd party libraries.  These are 
 libraries 
   that I've gotten directly from their source, and which 
 I've entered 
   in the repository through install:install-file.  I plan 
 to also put 
   my own released artifacts there.
  
   2)  A central-mirror repository that has just the things 
 that maven 
   needs (plugins and their dependencies).  This is the most 
 difficult 
   repository to manage, and a source of problems, as I find maven's 
   dependencies chaotic and unstable.  This is why I've 
 isolated them 
   from my other artifacts.
  
   D)  I plan to also use a snapshots repository that is 
 automatically 
   updated with my daily build artifacts.  In fact, I may simply 
   provide http access to the daily build's local repository.
   For now, I rebuild all of my artifacts locally.
  
   Alex
  
   On Fri, Nov 28, 2008 at 10:38 PM,
   [EMAIL PROTECTED] wrote:
  
Hi,
   
Is there any way to get the maven build process to 
 include a set 
of jars when compiling/packaging

Re: Third party jars

[Wayne Fay]

 Thanks for the suggestion, but I was already aware of this and I was
 wondering if there's an easier mechanism?   Such as mvn being smart with
 the jar name and coming up with the group/artifact ID, but I suspect
 that's beginning to ask too much!

This just isn't something Maven can help you with. Write a shell
script that receives the version and groupId, runs through all the
items named *.jar in the directoy, uses the file name as the
artifactId, and then outputs the dependencies list at the end after
using mvn install or mvn deploy on them. I know someone posted
something along these lines a while back on this list, but don't
remember specifics, so you can search the archives and try to find it.

If you do create something, please send it back to this list or put it
in the Maven Users Wiki so others can benefit in the future.

Wayne

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

RE: Third party jars

[John.Baker]

Hi,

Thanks for all the feedback.  I guess my reasoning was that inventing
the meta data (group/artifactId/version) for 20 jars is a little time
consuming - is there an easier way to do this?  I.e. Is there a maven
command to take a directory full of jars and upload them into my local
repository (~/.m2/repository) and generate a set of dependency
information for me?  Or even a pom with all the dependencies!


John 

 -Original Message-
 From: Alex Athanasopoulos [mailto:[EMAIL PROTECTED] 
 Sent: 29 November 2008 10:34
 To: Maven Users List
 Subject: Re: Third party jars
 
 Why not put the jars in a repository?  A repository is 
 perfect for containing 3rd party jars, and one of maven's 
 major benefits.  Once you do that, you don't need to refer to 
 the jars through a hardcoded path, but simply by a portable 
 artifact identifier.  You don't need any special tools or 
 repository managers, but you do need to setup your own remote 
 repository somehow.
 
 I simply use mvn install:install-file, and then copy the 
 generated files from my local repository to a remote 
 repository that I have created just for 3rd party libs.
 
 I'm fairly new to maven, and this is one of the first things 
 I had to do.
  The rest is just defining and managing repositories, which 
 can be a discussion of its own.  I'm not using any repository 
 managers yet (learning to live with maven is enough work for 
 me right now).  My A-B-Cs of repository management have been 
 the following:
 
 A)  At first I used only my local repository, which I shared 
 with other developers by putting it under version control in 
 svn, just like I had my
 3rd party libs before maven.   I used mvn -o most of the 
 time, to avoid
 accessing Maven's central repository.  I was a bit annoyed 
 that I had to use -o.  I tried to use the offline 
 configuration in settings.xml, but I couldn't get it to work 
 (one of my first frustrations with maven).  mvn -o worked 
 reliably, but I had to remember to use it.  Whenever I needed 
 a piece of Maven that I didn't have, I used mvn without the 
 -o flag, and once everything worked, I added the new 
 artifacts from my local repository to svn.  I did not add my 
 snapshots.
 
 B)  I then figured out how to avoid the -o flag, by defining 
 a mirror of the central repository in my settings.xml.  The 
 mirror was simply an http-accessible location of the single 
 svn-managed repository that I had.
  Whenever I needed to use a new piece of maven, I commented 
 out the mirror specifiction in my settings.xml, ran mvn so it 
 could get new pieces from repo1.maven.org, and then took the 
 comment out of settings.xml.  The rest was as in A.
 
 C)  I now use two repositories:
 1)  A repository of non-maven released artifacts.  
 Essentially this contains 3rd party libraries.  These are 
 libraries that I've gotten directly from their source, and 
 which I've entered in the repository through 
 install:install-file.  I plan to also put my own released 
 artifacts there.
 
 2)  A central-mirror repository that has just the things that 
 maven needs (plugins and their dependencies).  This is the 
 most difficult repository to manage, and a source of 
 problems, as I find maven's dependencies chaotic and 
 unstable.  This is why I've isolated them from my other artifacts.
 
 D)  I plan to also use a snapshots repository that is 
 automatically updated with my daily build artifacts.  In 
 fact, I may simply provide http access to the daily build's 
 local repository.
 For now, I rebuild all of my artifacts locally.
 
 Alex
 
 On Fri, Nov 28, 2008 at 10:38 PM, 
 [EMAIL PROTECTED] wrote:
 
  Hi,
 
  Is there any way to get the maven build process to include a set of 
  jars when compiling/packaging that are not in the 
 repository?  I have 
  some vendor jars and I don't fancy packing them all up and placing 
  them into the repository - I just want to point maven at a 
 lib directory?
 
  Thanks,
 
 
  john
  ___
 
  This e-mail may contain information that is confidential, 
 privileged 
  or otherwise protected from disclosure. If you are not an intended 
  recipient of this e-mail, do not duplicate or redistribute 
 it by any 
  means. Please delete it and any attachments and notify the 
 sender that 
  you have received it in error. Unless specifically indicated, this 
  e-mail is not an offer to buy or sell or a solicitation to 
 buy or sell 
  any securities, investment products or other financial product or 
  service, an official confirmation of any transaction, or an 
 official 
  statement of Barclays. Any views or opinions presented are solely 
  those of the author and do not necessarily represent those of 
  Barclays. This e-mail is subject to terms available at the 
 following 
  link: www.barcap.com/emaildisclaimer. By messaging with 
 Barclays you 
  consent to the foregoing.  Barclays Capital is the 
 investment banking 
  division of Barclays Bank PLC

Re: Third party jars

[Stephen Connolly]

mvn deploy:deploy-file -DgroupId=foo -DartifactId=bar -Dversion=1.0-foo
-Dpackaging=jar -DgeneratePom=true -Dfile=foo.jar ...

And with newer versions of the maven-deploy-plugin, generatePom defaults to
true.

It should be trivial for you to write a shell script or batch file that
loops through all the jar files in a directory and just calls mvn to do the
deploy for you.

(BTW, the generated pom is a minimal pom, and does not specify dependencies,
but you just want to pull them all in, so it will work for you and get you
up and running)

-Stephen

2008/12/1 [EMAIL PROTECTED]

 Hi,

 Thanks for all the feedback.  I guess my reasoning was that inventing
 the meta data (group/artifactId/version) for 20 jars is a little time
 consuming - is there an easier way to do this?  I.e. Is there a maven
 command to take a directory full of jars and upload them into my local
 repository (~/.m2/repository) and generate a set of dependency
 information for me?  Or even a pom with all the dependencies!


 John

  -Original Message-
  From: Alex Athanasopoulos [mailto:[EMAIL PROTECTED]
  Sent: 29 November 2008 10:34
  To: Maven Users List
  Subject: Re: Third party jars
 
  Why not put the jars in a repository?  A repository is
  perfect for containing 3rd party jars, and one of maven's
  major benefits.  Once you do that, you don't need to refer to
  the jars through a hardcoded path, but simply by a portable
  artifact identifier.  You don't need any special tools or
  repository managers, but you do need to setup your own remote
  repository somehow.
 
  I simply use mvn install:install-file, and then copy the
  generated files from my local repository to a remote
  repository that I have created just for 3rd party libs.
 
  I'm fairly new to maven, and this is one of the first things
  I had to do.
   The rest is just defining and managing repositories, which
  can be a discussion of its own.  I'm not using any repository
  managers yet (learning to live with maven is enough work for
  me right now).  My A-B-Cs of repository management have been
  the following:
 
  A)  At first I used only my local repository, which I shared
  with other developers by putting it under version control in
  svn, just like I had my
  3rd party libs before maven.   I used mvn -o most of the
  time, to avoid
  accessing Maven's central repository.  I was a bit annoyed
  that I had to use -o.  I tried to use the offline
  configuration in settings.xml, but I couldn't get it to work
  (one of my first frustrations with maven).  mvn -o worked
  reliably, but I had to remember to use it.  Whenever I needed
  a piece of Maven that I didn't have, I used mvn without the
  -o flag, and once everything worked, I added the new
  artifacts from my local repository to svn.  I did not add my
  snapshots.
 
  B)  I then figured out how to avoid the -o flag, by defining
  a mirror of the central repository in my settings.xml.  The
  mirror was simply an http-accessible location of the single
  svn-managed repository that I had.
   Whenever I needed to use a new piece of maven, I commented
  out the mirror specifiction in my settings.xml, ran mvn so it
  could get new pieces from repo1.maven.org, and then took the
  comment out of settings.xml.  The rest was as in A.
 
  C)  I now use two repositories:
  1)  A repository of non-maven released artifacts.
  Essentially this contains 3rd party libraries.  These are
  libraries that I've gotten directly from their source, and
  which I've entered in the repository through
  install:install-file.  I plan to also put my own released
  artifacts there.
 
  2)  A central-mirror repository that has just the things that
  maven needs (plugins and their dependencies).  This is the
  most difficult repository to manage, and a source of
  problems, as I find maven's dependencies chaotic and
  unstable.  This is why I've isolated them from my other artifacts.
 
  D)  I plan to also use a snapshots repository that is
  automatically updated with my daily build artifacts.  In
  fact, I may simply provide http access to the daily build's
  local repository.
  For now, I rebuild all of my artifacts locally.
 
  Alex
 
  On Fri, Nov 28, 2008 at 10:38 PM,
  [EMAIL PROTECTED] wrote:
 
   Hi,
  
   Is there any way to get the maven build process to include a set of
   jars when compiling/packaging that are not in the
  repository?  I have
   some vendor jars and I don't fancy packing them all up and placing
   them into the repository - I just want to point maven at a
  lib directory?
  
   Thanks,
  
  
   john
   ___
  
   This e-mail may contain information that is confidential,
  privileged
   or otherwise protected from disclosure. If you are not an intended
   recipient of this e-mail, do not duplicate or redistribute
  it by any
   means. Please delete it and any attachments and notify the
  sender that
   you have received it in error. Unless specifically indicated

Re: Third party jars

[Wayne Fay]

 consuming - is there an easier way to do this?  I.e. Is there a maven

Depend on fewer third-party jars...

But seriously, the first couple Maven projects are a little painful
due to things like this and the usual learning curve with a new tool,
but then it gets much easier.

Wayne

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

Re: Third party jars

[Alex Athanasopoulos]

Why not put the jars in a repository?  A repository is perfect for
containing 3rd party jars, and one of maven's major benefits.  Once you do
that, you don't need to refer to the jars through a hardcoded path, but
simply by a portable artifact identifier.  You don't need any special tools
or repository managers, but you do need to setup your own remote repository
somehow.

I simply use mvn install:install-file, and then copy the generated files
from my local repository to a remote repository that I have created just for
3rd party libs.

I'm fairly new to maven, and this is one of the first things I had to do.
 The rest is just defining and managing repositories, which can be a
discussion of its own.  I'm not using any repository managers yet (learning
to live with maven is enough work for me right now).  My A-B-Cs of
repository management have been the following:

A)  At first I used only my local repository, which I shared with other
developers by putting it under version control in svn, just like I had my
3rd party libs before maven.   I used mvn -o most of the time, to avoid
accessing Maven's central repository.  I was a bit annoyed that I had to use
-o.  I tried to use the offline configuration in settings.xml, but I
couldn't get it to work (one of my first frustrations with maven).  mvn -o
worked reliably, but I had to remember to use it.  Whenever I needed a piece
of Maven that I didn't have, I used mvn without the -o flag, and once
everything worked, I added the new artifacts from my local repository to
svn.  I did not add my snapshots.

B)  I then figured out how to avoid the -o flag, by defining a mirror of the
central repository in my settings.xml.  The mirror was simply an
http-accessible location of the single svn-managed repository that I had.
 Whenever I needed to use a new piece of maven, I commented out the mirror
specifiction in my settings.xml, ran mvn so it could get new pieces from
repo1.maven.org, and then took the comment out of settings.xml.  The rest
was as in A.

C)  I now use two repositories:
1)  A repository of non-maven released artifacts.  Essentially this contains
3rd party libraries.  These are libraries that I've gotten directly from
their source, and which I've entered in the repository through
install:install-file.  I plan to also put my own released artifacts there.

2)  A central-mirror repository that has just the things that maven needs
(plugins and their dependencies).  This is the most difficult repository to
manage, and a source of problems, as I find maven's dependencies chaotic and
unstable.  This is why I've isolated them from my other artifacts.

D)  I plan to also use a snapshots repository that is automatically updated
with my daily build artifacts.  In fact, I may simply provide http access to
the daily build's local repository.
For now, I rebuild all of my artifacts locally.

Alex

On Fri, Nov 28, 2008 at 10:38 PM, [EMAIL PROTECTED] wrote:

 Hi,

 Is there any way to get the maven build process to include a set of jars
 when compiling/packaging that are not in the repository?  I have some
 vendor jars and I don't fancy packing them all up and placing them into
 the repository - I just want to point maven at a lib directory?

 Thanks,


 john
 ___

 This e-mail may contain information that is confidential, privileged or
 otherwise protected from disclosure. If you are not an intended recipient of
 this e-mail, do not duplicate or redistribute it by any means. Please delete
 it and any attachments and notify the sender that you have received it in
 error. Unless specifically indicated, this e-mail is not an offer to buy or
 sell or a solicitation to buy or sell any securities, investment products or
 other financial product or service, an official confirmation of any
 transaction, or an official statement of Barclays. Any views or opinions
 presented are solely those of the author and do not necessarily represent
 those of Barclays. This e-mail is subject to terms available at the
 following link: www.barcap.com/emaildisclaimer. By messaging with Barclays
 you consent to the foregoing.  Barclays Capital is the investment banking
 division of Barclays Bank PLC, a company registered in England (number
 1026167) with its registered office at 1 Churchill Place, London, E14 5HP.
  This email may relate to or be sent from other members of the Barclays
 Group.
 ___

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

Re: Third party jars

[Brian Fox]

You could save youself a lot of hassle with a repo manager. You  
shouldn't use local repos as remote repos because the metadata is  
different. Also with unmanaged repos, snapshot accumulation will  
become a problem.


--Brian (mobile)


On Nov 29, 2008, at 5:33 AM, Alex Athanasopoulos [EMAIL PROTECTED] 
 wrote:



Why not put the jars in a repository?  A repository is perfect for
containing 3rd party jars, and one of maven's major benefits.  Once  
you do
that, you don't need to refer to the jars through a hardcoded path,  
but
simply by a portable artifact identifier.  You don't need any  
special tools
or repository managers, but you do need to setup your own remote  
repository

somehow.

I simply use mvn install:install-file, and then copy the generated  
files
from my local repository to a remote repository that I have created  
just for

3rd party libs.

I'm fairly new to maven, and this is one of the first things I had  
to do.

 The rest is just defining and managing repositories, which can be a
discussion of its own.  I'm not using any repository managers yet  
(learning

to live with maven is enough work for me right now).  My A-B-Cs of
repository management have been the following:

A)  At first I used only my local repository, which I shared with  
other
developers by putting it under version control in svn, just like I  
had my
3rd party libs before maven.   I used mvn -o most of the time, to  
avoid
accessing Maven's central repository.  I was a bit annoyed that I  
had to use

-o.  I tried to use the offline configuration in settings.xml, but I
couldn't get it to work (one of my first frustrations with maven).   
mvn -o
worked reliably, but I had to remember to use it.  Whenever I needed  
a piece

of Maven that I didn't have, I used mvn without the -o flag, and once
everything worked, I added the new artifacts from my local  
repository to

svn.  I did not add my snapshots.

B)  I then figured out how to avoid the -o flag, by defining a  
mirror of the

central repository in my settings.xml.  The mirror was simply an
http-accessible location of the single svn-managed repository that I  
had.
 Whenever I needed to use a new piece of maven, I commented out the  
mirror
specifiction in my settings.xml, ran mvn so it could get new pieces  
from
repo1.maven.org, and then took the comment out of settings.xml.  The  
rest

was as in A.

C)  I now use two repositories:
1)  A repository of non-maven released artifacts.  Essentially this  
contains
3rd party libraries.  These are libraries that I've gotten directly  
from

their source, and which I've entered in the repository through
install:install-file.  I plan to also put my own released artifacts  
there.


2)  A central-mirror repository that has just the things that maven  
needs
(plugins and their dependencies).  This is the most difficult  
repository to
manage, and a source of problems, as I find maven's dependencies  
chaotic and

unstable.  This is why I've isolated them from my other artifacts.

D)  I plan to also use a snapshots repository that is automatically  
updated
with my daily build artifacts.  In fact, I may simply provide http  
access to

the daily build's local repository.
For now, I rebuild all of my artifacts locally.

Alex

On Fri, Nov 28, 2008 at 10:38 PM, [EMAIL PROTECTED]  
wrote:


 Hi,

 Is there any way to get the maven build process to include a set  
of jars
 when compiling/packaging that are not in the repository?  I have  
some
 vendor jars and I don't fancy packing them all up and placing them  
into

 the repository - I just want to point maven at a lib directory?

 Thanks,


 john
 ___

 This e-mail may contain information that is confidential,  
privileged or
 otherwise protected from disclosure. If you are not an intended  
recipient of
 this e-mail, do not duplicate or redistribute it by any means.  
Please delete
 it and any attachments and notify the sender that you have  
received it in
 error. Unless specifically indicated, this e-mail is not an offer  
to buy or
 sell or a solicitation to buy or sell any securities, investment  
products or

 other financial product or service, an official confirmation of any
 transaction, or an official statement of Barclays. Any views or  
opinions
 presented are solely those of the author and do not necessarily  
represent

 those of Barclays. This e-mail is subject to terms available at the
 following link: www.barcap.com/emaildisclaimer. By messaging with  
Barclays
 you consent to the foregoing.  Barclays Capital is the investment  
banking
 division of Barclays Bank PLC, a company registered in England  
(number
 1026167) with its registered office at 1 Churchill Place, London,  
E14 5HP.
  This email may relate to or be sent from other members of the  
Barclays

 Group.
 ___

  
-

 To unsubscribe, 

Third party jars

[John.Baker]

Hi,

Is there any way to get the maven build process to include a set of jars
when compiling/packaging that are not in the repository?  I have some
vendor jars and I don't fancy packing them all up and placing them into
the repository - I just want to point maven at a lib directory?

Thanks,


john
___

This e-mail may contain information that is confidential, privileged or 
otherwise protected from disclosure. If you are not an intended recipient of 
this e-mail, do not duplicate or redistribute it by any means. Please delete it 
and any attachments and notify the sender that you have received it in error. 
Unless specifically indicated, this e-mail is not an offer to buy or sell or a 
solicitation to buy or sell any securities, investment products or other 
financial product or service, an official confirmation of any transaction, or 
an official statement of Barclays. Any views or opinions presented are solely 
those of the author and do not necessarily represent those of Barclays. This 
e-mail is subject to terms available at the following link: 
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the 
foregoing.  Barclays Capital is the investment banking division of Barclays 
Bank PLC, a company registered in England (number 1026167) with its registered 
office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be 
sent from other members of the Barclays Group.
___

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

Re: Third party jars

[David C. Hicks]

The assembly plugin can add arbitrary files to your package.


[EMAIL PROTECTED] wrote:

Hi,

Is there any way to get the maven build process to include a set of jars
when compiling/packaging that are not in the repository?  I have some
vendor jars and I don't fancy packing them all up and placing them into
the repository - I just want to point maven at a lib directory?

Thanks,


john
___

This e-mail may contain information that is confidential, privileged or 
otherwise protected from disclosure. If you are not an intended recipient of 
this e-mail, do not duplicate or redistribute it by any means. Please delete it 
and any attachments and notify the sender that you have received it in error. 
Unless specifically indicated, this e-mail is not an offer to buy or sell or a 
solicitation to buy or sell any securities, investment products or other 
financial product or service, an official confirmation of any transaction, or 
an official statement of Barclays. Any views or opinions presented are solely 
those of the author and do not necessarily represent those of Barclays. This 
e-mail is subject to terms available at the following link: 
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the 
foregoing.  Barclays Capital is the investment banking division of Barclays 
Bank PLC, a company registered in England (number 1026167) with its registered 
office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be 
sent from other members of the Barclays Group.
___

-
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: Third party jars

[John.Baker]

Excellent - do you happen to have a pom extract to, say, include the
contents of ./lib on the compile path? 

 -Original Message-
 From: David C. Hicks [mailto:[EMAIL PROTECTED] 
 Sent: 28 November 2008 20:45
 To: Maven Users List
 Subject: Re: Third party jars
 
 The assembly plugin can add arbitrary files to your package.
 
 
 [EMAIL PROTECTED] wrote:
  Hi,
 
  Is there any way to get the maven build process to include a set of 
  jars when compiling/packaging that are not in the 
 repository?  I have 
  some vendor jars and I don't fancy packing them all up and placing 
  them into the repository - I just want to point maven at a 
 lib directory?
 
  Thanks,
 
 
  john
  ___
 
  This e-mail may contain information that is confidential, 
 privileged or otherwise protected from disclosure. If you are 
 not an intended recipient of this e-mail, do not duplicate or 
 redistribute it by any means. Please delete it and any 
 attachments and notify the sender that you have received it 
 in error. Unless specifically indicated, this e-mail is not 
 an offer to buy or sell or a solicitation to buy or sell any 
 securities, investment products or other financial product or 
 service, an official confirmation of any transaction, or an 
 official statement of Barclays. Any views or opinions 
 presented are solely those of the author and do not 
 necessarily represent those of Barclays. This e-mail is 
 subject to terms available at the following link: 
 www.barcap.com/emaildisclaimer. By messaging with Barclays 
 you consent to the foregoing.  Barclays Capital is the 
 investment banking division of Barclays Bank PLC, a company 
 registered in England (number 1026167) with its registered 
 office at 1 Churchill Place, London, E14 5HP.  This email may 
 relate to or be sent from other members of the Barclays Group.
  ___
 
  
 -
  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]
 
 
___

This e-mail may contain information that is confidential, privileged or 
otherwise protected from disclosure. If you are not an intended recipient of 
this e-mail, do not duplicate or redistribute it by any means. Please delete it 
and any attachments and notify the sender that you have received it in error. 
Unless specifically indicated, this e-mail is not an offer to buy or sell or a 
solicitation to buy or sell any securities, investment products or other 
financial product or service, an official confirmation of any transaction, or 
an official statement of Barclays. Any views or opinions presented are solely 
those of the author and do not necessarily represent those of Barclays. This 
e-mail is subject to terms available at the following link: 
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the 
foregoing.  Barclays Capital is the investment banking division of Barclays 
Bank PLC, a company registered in England (number 1026167) with its registered 
office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be 
sent from other members of the Barclays Group.
___

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

Re: Third party jars

[David C. Hicks]

Sure.  The attached assembly.xml is used by the following profile.  The 
profile just makes sure that the assembly plugin runs during the 
package phase and includes all attached artifacts.  The real work is 
in the attached assembly.xml.


Dave

   profile
   idrelease_assembly/id
   build
   plugins
   plugin
   
artifactIdmaven-assembly-plugin/artifactId   
   configuration

   descriptorassembly.xml/descriptor
   /configuration
   executions
   execution
   idmake-assembly/id
   phasepackage/phase
   goals
   goalattached/goal
   /goals
   /execution
   /executions
   /plugin
   /plugins
   /build
   /profile


[EMAIL PROTECTED] wrote:

Excellent - do you happen to have a pom extract to, say, include the
contents of ./lib on the compile path? 

  

-Original Message-
From: David C. Hicks [mailto:[EMAIL PROTECTED] 
Sent: 28 November 2008 20:45

To: Maven Users List
Subject: Re: Third party jars

The assembly plugin can add arbitrary files to your package.


[EMAIL PROTECTED] wrote:


Hi,

Is there any way to get the maven build process to include a set of 
jars when compiling/packaging that are not in the 
  
repository?  I have 

some vendor jars and I don't fancy packing them all up and placing 
them into the repository - I just want to point maven at a 
  

lib directory?


Thanks,


john
___

This e-mail may contain information that is confidential, 
  
privileged or otherwise protected from disclosure. If you are 
not an intended recipient of this e-mail, do not duplicate or 
redistribute it by any means. Please delete it and any 
attachments and notify the sender that you have received it 
in error. Unless specifically indicated, this e-mail is not 
an offer to buy or sell or a solicitation to buy or sell any 
securities, investment products or other financial product or 
service, an official confirmation of any transaction, or an 
official statement of Barclays. Any views or opinions 
presented are solely those of the author and do not 
necessarily represent those of Barclays. This e-mail is 
subject to terms available at the following link: 
www.barcap.com/emaildisclaimer. By messaging with Barclays 
you consent to the foregoing.  Barclays Capital is the 
investment banking division of Barclays Bank PLC, a company 
registered in England (number 1026167) with its registered 
office at 1 Churchill Place, London, E14 5HP.  This email may 
relate to or be sent from other members of the Barclays Group.


___


  

-


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]




___

This e-mail may contain information that is confidential, privileged or 
otherwise protected from disclosure. If you are not an intended recipient of 
this e-mail, do not duplicate or redistribute it by any means. Please delete it 
and any attachments and notify the sender that you have received it in error. 
Unless specifically indicated, this e-mail is not an offer to buy or sell or a 
solicitation to buy or sell any securities, investment products or other 
financial product or service, an official confirmation of any transaction, or 
an official statement of Barclays. Any views or opinions presented are solely 
those of the author and do not necessarily represent those of Barclays. This 
e-mail is subject to terms available at the following link: 
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the 
foregoing.  Barclays Capital is the investment banking division of Barclays 
Bank PLC, a company registered in England (number 1026167) with its registered 
office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be 
sent from other members of the Barclays Group.
___

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

  
assembly
idassembly/id
formats
formatzip/format
/formats
fileSets
fileSet
directorytarget/directory
filteredfalse/filtered
includes
include*.war/include

RE: Third party jars

[Brian E. Fox]

This won't help when compiling though. The best way is to get them into
an internal repo...something like Nexus. You can just upload it directly
via the ui and it will make the pom for you if you don't want to. (I
believe the others can do it as well)

-Original Message-
From: David C. Hicks [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 28, 2008 3:54 PM
To: Maven Users List
Subject: Re: Third party jars

Sure.  The attached assembly.xml is used by the following profile.  The
profile just makes sure that the assembly plugin runs during the
package phase and includes all attached artifacts.  The real work is
in the attached assembly.xml.

Dave

profile
idrelease_assembly/id
build
plugins
plugin

artifactIdmaven-assembly-plugin/artifactId   
configuration
descriptorassembly.xml/descriptor
/configuration
executions
execution
idmake-assembly/id
phasepackage/phase
goals
goalattached/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/profile


[EMAIL PROTECTED] wrote:
 Excellent - do you happen to have a pom extract to, say, include the 
 contents of ./lib on the compile path?

   
 -Original Message-
 From: David C. Hicks [mailto:[EMAIL PROTECTED]
 Sent: 28 November 2008 20:45
 To: Maven Users List
 Subject: Re: Third party jars

 The assembly plugin can add arbitrary files to your package.


 [EMAIL PROTECTED] wrote:
 
 Hi,

 Is there any way to get the maven build process to include a set of 
 jars when compiling/packaging that are not in the
   
 repository?  I have
 
 some vendor jars and I don't fancy packing them all up and placing 
 them into the repository - I just want to point maven at a
   
 lib directory?
 
 Thanks,


 john
 ___

 This e-mail may contain information that is confidential,
   
 privileged or otherwise protected from disclosure. If you are not an 
 intended recipient of this e-mail, do not duplicate or redistribute 
 it by any means. Please delete it and any attachments and notify the 
 sender that you have received it in error. Unless specifically 
 indicated, this e-mail is not an offer to buy or sell or a 
 solicitation to buy or sell any securities, investment products or 
 other financial product or service, an official confirmation of any 
 transaction, or an official statement of Barclays. Any views or 
 opinions presented are solely those of the author and do not 
 necessarily represent those of Barclays. This e-mail is subject to 
 terms available at the following link:
 www.barcap.com/emaildisclaimer. By messaging with Barclays you 
 consent to the foregoing.  Barclays Capital is the investment banking

 division of Barclays Bank PLC, a company registered in England 
 (number 1026167) with its registered office at 1 Churchill Place, 
 London, E14 5HP.  This email may relate to or be sent from other 
 members of the Barclays Group.
 
 ___


   
 -
 
 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]


 
 ___

 This e-mail may contain information that is confidential, privileged
or otherwise protected from disclosure. If you are not an intended
recipient of this e-mail, do not duplicate or redistribute it by any
means. Please delete it and any attachments and notify the sender that
you have received it in error. Unless specifically indicated, this
e-mail is not an offer to buy or sell or a solicitation to buy or sell
any securities, investment products or other financial product or
service, an official confirmation of any transaction, or an official
statement of Barclays. Any views or opinions presented are solely those
of the author and do not necessarily represent those of Barclays. This
e-mail is subject to terms available at the following link:
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent
to the foregoing.  Barclays Capital is the investment banking division
of Barclays Bank PLC, a company registered in England (number 1026167)
with its registered office at 1 Churchill Place, London, E14 5HP.  This
email may relate to or be sent from other members of the Barclays Group

Re: Third party jars

[David C. Hicks]

Oops!  I missed the part about compiling.  True, that won't help if you 
need those jars for the actual build.  Nexus would be my suggestion for 
that.  Easy to install and maintain.  I just set it up at my company a 
couple of weeks ago.



Brian E. Fox wrote:

This won't help when compiling though. The best way is to get them into
an internal repo...something like Nexus. You can just upload it directly
via the ui and it will make the pom for you if you don't want to. (I
believe the others can do it as well)


  


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

RE: Third party jars

[Todd Thiessen]

I am curious about this myself.  I have Nexus running but I don't see an
option in the UI to upload a jar.  I was hopeful of somekind of option
like this that would create the pom and all metadata files that go along
with it.

Or is there a Maven command to deploy a third party jar to the repo? 


---
Todd Thiessen

-Original Message-
From: David C. Hicks [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 28, 2008 4:09 PM
To: Maven Users List
Subject: Re: Third party jars

Oops!  I missed the part about compiling.  True, that won't help if you
need those jars for the actual build.  Nexus would be my suggestion for
that.  Easy to install and maintain.  I just set it up at my company a
couple of weeks ago.


Brian E. Fox wrote:
 This won't help when compiling though. The best way is to get them 
 into an internal repo...something like Nexus. You can just upload it 
 directly via the ui and it will make the pom for you if you don't want

 to. (I believe the others can do it as well)


   

-
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: Third party jars

[Brian E. Fox]

Right click on a hosted release repository in the browse repo screen. If
you have proper permissions, you'll see the option.

See here for more:
http://books.sonatype.com/maven-book/reference/repository-manager.html#s
ect-upload-asset-ui

-Original Message-
From: Todd Thiessen [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 28, 2008 4:13 PM
To: Maven Users List
Subject: RE: Third party jars

I am curious about this myself.  I have Nexus running but I don't see an
option in the UI to upload a jar.  I was hopeful of somekind of option
like this that would create the pom and all metadata files that go along
with it.

Or is there a Maven command to deploy a third party jar to the repo? 


---
Todd Thiessen

-Original Message-
From: David C. Hicks [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 28, 2008 4:09 PM
To: Maven Users List
Subject: Re: Third party jars

Oops!  I missed the part about compiling.  True, that won't help if you
need those jars for the actual build.  Nexus would be my suggestion for
that.  Easy to install and maintain.  I just set it up at my company a
couple of weeks ago.


Brian E. Fox wrote:
 This won't help when compiling though. The best way is to get them 
 into an internal repo...something like Nexus. You can just upload it 
 directly via the ui and it will make the pom for you if you don't want

 to. (I believe the others can do it as well)


   

-
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: Third party jars

[Todd Thiessen]

SWEET I can't believe I missed that.

Thanks. 

---
Todd Thiessen

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 28, 2008 4:18 PM
To: Maven Users List
Subject: RE: Third party jars

Right click on a hosted release repository in the browse repo screen. If
you have proper permissions, you'll see the option.

See here for more:
http://books.sonatype.com/maven-book/reference/repository-manager.html#s
ect-upload-asset-ui

-Original Message-
From: Todd Thiessen [mailto:[EMAIL PROTECTED]
Sent: Friday, November 28, 2008 4:13 PM
To: Maven Users List
Subject: RE: Third party jars

I am curious about this myself.  I have Nexus running but I don't see an
option in the UI to upload a jar.  I was hopeful of somekind of option
like this that would create the pom and all metadata files that go along
with it.

Or is there a Maven command to deploy a third party jar to the repo? 


---
Todd Thiessen

-Original Message-
From: David C. Hicks [mailto:[EMAIL PROTECTED]
Sent: Friday, November 28, 2008 4:09 PM
To: Maven Users List
Subject: Re: Third party jars

Oops!  I missed the part about compiling.  True, that won't help if you
need those jars for the actual build.  Nexus would be my suggestion for
that.  Easy to install and maintain.  I just set it up at my company a
couple of weeks ago.


Brian E. Fox wrote:
 This won't help when compiling though. The best way is to get them 
 into an internal repo...something like Nexus. You can just upload it 
 directly via the ui and it will make the pom for you if you don't want

 to. (I believe the others can do it as well)


   

-
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: Third party jars

[Graham Leggett]

[EMAIL PROTECTED] wrote:


Is there any way to get the maven build process to include a set of jars
when compiling/packaging that are not in the repository?  I have some
vendor jars and I don't fancy packing them all up and placing them into
the repository - I just want to point maven at a lib directory?


Ideally you want to host for yourself a project wide maven repository, 
both to place your released artifacts into, and place the third party 
vendor jars into.


This guarantees that someone other than you can build the code, without 
encountering an error or complaints about missing jars.


Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature

installing third party jars to local repository issue

[Ricky]

Hi,

I ran the following command :

mvn install:install-file
-Dfile=c:\project\crystal\cr4e\concurrent\1.0\concurrent-1.0.jar
-DgroupId=com.crystal -Dversion=1.0   -DgeneratePom=true
-DcreateChecksum=true -Dclassifier=sources -DcreateChecksum=true
-Dclassifier=sources  -Dpackaging=jar -DartifactId=cr4e-concurrent

to install concurrent jar file on my local repository;It worked as i noticed
that it generated valid .pom, sha1 files and created folder structure
necessary.

However when i referenced the same jar with group id, artifact id matching
as in :

dependency
groupIdcom.crystal/groupId
artifactIdcr4e-concurrent/artifactId
version1.0/version
/dependency

It looks for dependency *NOT in local repository but in repo1.maven.org or
Archiva repository of our organization* and then it fails to find it. In my
conf\settings.xml file; i have
localRepository/Org_Name_Here/java/maven/repository/localRepository, but
i have commented out all mirrors that were being used for looking at
repositories outside.

However Still maven is *NOT *looking for jars in local repository and it
fails to find the artifact and tells me to run install:install-file to
install the artifact. Am i missing something?

Any help would be appreciable ...

Regards
Vyas, Anirudh
||  ॐ  ||

Re: installing third party jars to local repository issue

[Stevo Slavić]

Hello RIcky,

Remove -Dclassifier=sources, both of them, as you are not installing
sources but binaries.

Regards,
Stevo.

On Fri, Oct 24, 2008 at 2:00 PM, Ricky [EMAIL PROTECTED] wrote:

 Hi,

 I ran the following command :

 mvn install:install-file
 -Dfile=c:\project\crystal\cr4e\concurrent\1.0\concurrent-1.0.jar
 -DgroupId=com.crystal -Dversion=1.0   -DgeneratePom=true
 -DcreateChecksum=true -Dclassifier=sources -DcreateChecksum=true
 -Dclassifier=sources  -Dpackaging=jar -DartifactId=cr4e-concurrent

 to install concurrent jar file on my local repository;It worked as i
 noticed
 that it generated valid .pom, sha1 files and created folder structure
 necessary.

 However when i referenced the same jar with group id, artifact id matching
 as in :

 dependency
groupIdcom.crystal/groupId
artifactIdcr4e-concurrent/artifactId
version1.0/version
/dependency

 It looks for dependency *NOT in local repository but in repo1.maven.org or
 Archiva repository of our organization* and then it fails to find it. In my
 conf\settings.xml file; i have
 localRepository/Org_Name_Here/java/maven/repository/localRepository,
 but
 i have commented out all mirrors that were being used for looking at
 repositories outside.

 However Still maven is *NOT *looking for jars in local repository and it
 fails to find the artifact and tells me to run install:install-file to
 install the artifact. Am i missing something?

 Any help would be appreciable ...

 Regards
 Vyas, Anirudh
 ||  ॐ  ||

Re: installing third party jars to local repository issue

[Ricky]

Stevo,

Your the man! :-) ... removing -Dclassifier=sources works and your
explanation makes sense too.

Thanks a Lot, appreciate it.
Rick

On Fri, Oct 24, 2008 at 8:08 AM, Stevo Slavić [EMAIL PROTECTED] wrote:

 Hello RIcky,

 Remove -Dclassifier=sources, both of them, as you are not installing
 sources but binaries.

 Regards,
 Stevo.

 On Fri, Oct 24, 2008 at 2:00 PM, Ricky [EMAIL PROTECTED] wrote:

  Hi,
 
  I ran the following command :
 
  mvn install:install-file
  -Dfile=c:\project\crystal\cr4e\concurrent\1.0\concurrent-1.0.jar
  -DgroupId=com.crystal -Dversion=1.0   -DgeneratePom=true
  -DcreateChecksum=true -Dclassifier=sources -DcreateChecksum=true
  -Dclassifier=sources  -Dpackaging=jar -DartifactId=cr4e-concurrent
 
  to install concurrent jar file on my local repository;It worked as i
  noticed
  that it generated valid .pom, sha1 files and created folder structure
  necessary.
 
  However when i referenced the same jar with group id, artifact id
 matching
  as in :
 
  dependency
 groupIdcom.crystal/groupId
 artifactIdcr4e-concurrent/artifactId
 version1.0/version
 /dependency
 
  It looks for dependency *NOT in local repository but in repo1.maven.orgor
  Archiva repository of our organization* and then it fails to find it. In
 my
  conf\settings.xml file; i have
  localRepository/Org_Name_Here/java/maven/repository/localRepository,
  but
  i have commented out all mirrors that were being used for looking at
  repositories outside.
 
  However Still maven is *NOT *looking for jars in local repository and it
  fails to find the artifact and tells me to run install:install-file to
  install the artifact. Am i missing something?
 
  Any help would be appreciable ...
 
  Regards
  Vyas, Anirudh
  ||  ॐ  ||

RE: converting from maven1 to maven2, pom for third party jars?

[nicklist]

I can't repeat it often enough: do not copy a local repository to be used as a 
remote repository. There is not the same information in your local repository 
as in your remote repository.

Really, do use a Maven repository / mirror, like Archiva, Artifactory or 
Nexus/Proximity.

Hth,

Nick S.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thu 3/6/2008 07:04
To: Maven Users List
Subject: Re: converting from maven1 to maven2, pom for third party jars?
 
To be able to deploy something on your company's remote server,
have a look at Distribution Management.

What I do for those external jars is - on the console, when maven doesn't find 
a depdency, it always gives you the exact String you need to use to install it 
on your local server or to deploy it on your company's remote server. I always 
copy this String from the console, then edit it in a text editor, put the jar 
in the same folder as the pom, add the name of the pom to the end of the 
String, hit enter, the jar gets installed, its poms and checksums created, when 
done, I delete the jar I put in the project's folder.

I've never tried the deploy option, as I am planning to copy my entire local 
repository to the remote one, as soon as I am finished migrating to Maven 2. 
The install version works perfectly (and I am sure when you set up distribution 
management, this works perfectly too).
To set up Distribution Management, Add it to your pom, then set the login 
information in your setting.xml, though I wouldn't recommend you to leave away 
the password - a) for security reasons b) so that noone can accidently upload 
something to your repository...

Hope that helps,

Christine
 Original-Nachricht 
 Datum: Wed, 05 Mar 2008 23:29:53 +0100
 Von: david delbecq [EMAIL PROTECTED]
 An: Maven Users List users@maven.apache.org
 Betreff: Re: converting from maven1 to maven2, pom for third party jars?

 Did :) does not work, will investigate further. For now am doing 
 scripted convertion server side, attackign directly the server 
 direcgtory structure using install-file, works like a charm :D
 
 Nick Stolwijk a écrit :
  Take a look at the repositoryId [1] option of deploy-file and the 
  server section in settings.xml [2]. They should take care of your 
  authorisation.
 
  Hth,
 
  Nick Stolwijk
 
  [1] 
 
 http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId
  
 
  [2] 
 
 http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_server 
 
 
  delbd wrote:
  the deploy target doesnt seem to accept the fact our local repository 
  requires password authentification. it just fails. Our server ask 
  client for credential for write operation (apache DAV mod) but maven 
  doesn't try with password. i'll give a try using install:install-file 
  thanks
 
 
 
  [EMAIL PROTECTED] a écrit :
  There is a solution for this problem. The deploy:deploy-file will 
  automatically generate a pom file.
 
  So, remove the jars from your remote repository and deploy them 
  again with mvn deploy:deploy-file .
 
  Perhaps if you make a list with the directories it should be 
  possible to create a little script to do it.
 
  Hth,
 
  Nick S.
 
 
  -Original Message-
  From: David Delbecq [mailto:[EMAIL PROTECTED]
  Sent: Wed 3/5/2008 16:27
  To: Maven Users List
  Subject: converting from maven1 to maven2, pom for third party jars?
   
  Hello,
 
  in the process of converting our app from maven1 to maven2, we 
  changed our repository to have maven2 structure. For most library we 
  use public repositories (maven, jboss, apache) to fetch files. But 
  from some libraries we had to make them available to our local 
  repository, moving the jar from his group/jars/artefact-version.jar 
  to group/artifact/version/artifact-version.jar.
 
  However, for the jar there is no pom files coming along, just a 
  jar. maven2 has no special trouble handling them, except it keeps 
  trying to go to all our configured repositories and try to download 
  those inexistant pom:
   
  Downloading: 
 
 http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
 
  Downloading: 
 
 http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
 
  Downloading: 
 
 http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
 
  Downloading: 
 
 http://repository.jboss.com/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
 
  Downloading: 
 
 http://repo1.maven.org/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
 
  Downloading: 
 
 http://xxx/repository/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
  
 
  Downloading: 
 
 http://download.java.net/maven/2//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
  
 
  Downloading: 
 
 http://archiva.openqa.org/repository/releases//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1

Re: RE: converting from maven1 to maven2, pom for third party jars?

[Dooing]

So what else do you recommend me to easily get all required dependencies on the 
remote server - at once if possible?

What would / could happen if I simply copied the local repository to the remote 
one?

Thanks in advance,

Stefanie

 Original-Nachricht 
 Datum: Thu, 6 Mar 2008 09:10:48 +0100
 Von: [EMAIL PROTECTED]
 An: Maven Users List users@maven.apache.org
 Betreff: RE: converting from maven1 to maven2, pom for third party jars?

 I can't repeat it often enough: do not copy a local repository to be used
 as a remote repository. There is not the same information in your local
 repository as in your remote repository.
 
 Really, do use a Maven repository / mirror, like Archiva, Artifactory or
 Nexus/Proximity.
 
 Hth,
 
 Nick S.
 
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Thu 3/6/2008 07:04
 To: Maven Users List
 Subject: Re: converting from maven1 to maven2, pom for third party jars?
  
 To be able to deploy something on your company's remote server,
 have a look at Distribution Management.
 
 What I do for those external jars is - on the console, when maven doesn't
 find a depdency, it always gives you the exact String you need to use to
 install it on your local server or to deploy it on your company's remote
 server. I always copy this String from the console, then edit it in a text
 editor, put the jar in the same folder as the pom, add the name of the pom to
 the end of the String, hit enter, the jar gets installed, its poms and
 checksums created, when done, I delete the jar I put in the project's folder.
 
 I've never tried the deploy option, as I am planning to copy my entire
 local repository to the remote one, as soon as I am finished migrating to
 Maven 2. The install version works perfectly (and I am sure when you set up
 distribution management, this works perfectly too).
 To set up Distribution Management, Add it to your pom, then set the login
 information in your setting.xml, though I wouldn't recommend you to leave
 away the password - a) for security reasons b) so that noone can accidently
 upload something to your repository...
 
 Hope that helps,
 
 Christine
  Original-Nachricht 
  Datum: Wed, 05 Mar 2008 23:29:53 +0100
  Von: david delbecq [EMAIL PROTECTED]
  An: Maven Users List users@maven.apache.org
  Betreff: Re: converting from maven1 to maven2, pom for third party jars?
 
  Did :) does not work, will investigate further. For now am doing 
  scripted convertion server side, attackign directly the server 
  direcgtory structure using install-file, works like a charm :D
  
  Nick Stolwijk a écrit :
   Take a look at the repositoryId [1] option of deploy-file and the 
   server section in settings.xml [2]. They should take care of your 
   authorisation.
  
   Hth,
  
   Nick Stolwijk
  
   [1] 
  
 
 http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId
  
  
   [2] 
  
 
 http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_server 
  
  
   delbd wrote:
   the deploy target doesnt seem to accept the fact our local repository
   requires password authentification. it just fails. Our server ask 
   client for credential for write operation (apache DAV mod) but maven 
   doesn't try with password. i'll give a try using install:install-file
   thanks
  
  
  
   [EMAIL PROTECTED] a écrit :
   There is a solution for this problem. The deploy:deploy-file will 
   automatically generate a pom file.
  
   So, remove the jars from your remote repository and deploy them 
   again with mvn deploy:deploy-file .
  
   Perhaps if you make a list with the directories it should be 
   possible to create a little script to do it.
  
   Hth,
  
   Nick S.
  
  
   -Original Message-
   From: David Delbecq [mailto:[EMAIL PROTECTED]
   Sent: Wed 3/5/2008 16:27
   To: Maven Users List
   Subject: converting from maven1 to maven2, pom for third party jars?

   Hello,
  
   in the process of converting our app from maven1 to maven2, we 
   changed our repository to have maven2 structure. For most library we
   use public repositories (maven, jboss, apache) to fetch files. But 
   from some libraries we had to make them available to our local 
   repository, moving the jar from his group/jars/artefact-version.jar 
   to group/artifact/version/artifact-version.jar.
  
   However, for the jar there is no pom files coming along, just a 
   jar. maven2 has no special trouble handling them, except it keeps 
   trying to go to all our configured repositories and try to download 
   those inexistant pom:

   Downloading: 
  
 
 http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
  
   Downloading: 
  
 
 http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
  
   Downloading: 
  
 
 http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom

RE: RE: converting from maven1 to maven2, pom for third party jars?

[nicklist]

I would setup a maven repository, with mirrors for at least central and maybe 
some other repositories. Also create inhouse repositories for your own release, 
Snapshots and external dependencies. (3 different repositories)

Then set up your local maven to use the mirrors, and rebuild with an empty 
local repository. For every dependency that is not found, use the same tactics 
as you did, but then with deploy:deploy-file deploy them to the external 
dependency repository and add the remote repository to the repository section 
in the pom file.

The way local and remote repositories are different, for example:

- Local snapshots are not saved with timestamp, remote snapshots are saved with 
timestamps. If you use a local repository as remote repository, maven can't 
tell if a SNAPSHOT has changed and won't download newer SNAPSHOTS.

Hth,

Nick S.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thu 3/6/2008 09:34
To: Maven Users List
Subject: Re: RE: converting from maven1 to maven2, pom for third party jars?
 
So what else do you recommend me to easily get all required dependencies on the 
remote server - at once if possible?

What would / could happen if I simply copied the local repository to the remote 
one?

Thanks in advance,

Stefanie

 Original-Nachricht 
 Datum: Thu, 6 Mar 2008 09:10:48 +0100
 Von: [EMAIL PROTECTED]
 An: Maven Users List users@maven.apache.org
 Betreff: RE: converting from maven1 to maven2, pom for third party jars?

 I can't repeat it often enough: do not copy a local repository to be used
 as a remote repository. There is not the same information in your local
 repository as in your remote repository.
 
 Really, do use a Maven repository / mirror, like Archiva, Artifactory or
 Nexus/Proximity.
 
 Hth,
 
 Nick S.
 
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Thu 3/6/2008 07:04
 To: Maven Users List
 Subject: Re: converting from maven1 to maven2, pom for third party jars?
  
 To be able to deploy something on your company's remote server,
 have a look at Distribution Management.
 
 What I do for those external jars is - on the console, when maven doesn't
 find a depdency, it always gives you the exact String you need to use to
 install it on your local server or to deploy it on your company's remote
 server. I always copy this String from the console, then edit it in a text
 editor, put the jar in the same folder as the pom, add the name of the pom to
 the end of the String, hit enter, the jar gets installed, its poms and
 checksums created, when done, I delete the jar I put in the project's folder.
 
 I've never tried the deploy option, as I am planning to copy my entire
 local repository to the remote one, as soon as I am finished migrating to
 Maven 2. The install version works perfectly (and I am sure when you set up
 distribution management, this works perfectly too).
 To set up Distribution Management, Add it to your pom, then set the login
 information in your setting.xml, though I wouldn't recommend you to leave
 away the password - a) for security reasons b) so that noone can accidently
 upload something to your repository...
 
 Hope that helps,
 
 Christine
  Original-Nachricht 
  Datum: Wed, 05 Mar 2008 23:29:53 +0100
  Von: david delbecq [EMAIL PROTECTED]
  An: Maven Users List users@maven.apache.org
  Betreff: Re: converting from maven1 to maven2, pom for third party jars?
 
  Did :) does not work, will investigate further. For now am doing 
  scripted convertion server side, attackign directly the server 
  direcgtory structure using install-file, works like a charm :D
  
  Nick Stolwijk a écrit :
   Take a look at the repositoryId [1] option of deploy-file and the 
   server section in settings.xml [2]. They should take care of your 
   authorisation.
  
   Hth,
  
   Nick Stolwijk
  
   [1] 
  
 
 http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId
  
  
   [2] 
  
 
 http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_server 
  
  
   delbd wrote:
   the deploy target doesnt seem to accept the fact our local repository
   requires password authentification. it just fails. Our server ask 
   client for credential for write operation (apache DAV mod) but maven 
   doesn't try with password. i'll give a try using install:install-file
   thanks
  
  
  
   [EMAIL PROTECTED] a écrit :
   There is a solution for this problem. The deploy:deploy-file will 
   automatically generate a pom file.
  
   So, remove the jars from your remote repository and deploy them 
   again with mvn deploy:deploy-file .
  
   Perhaps if you make a list with the directories it should be 
   possible to create a little script to do it.
  
   Hth,
  
   Nick S.
  
  
   -Original Message-
   From: David Delbecq [mailto:[EMAIL PROTECTED]
   Sent: Wed 3/5/2008 16:27
   To: Maven Users List
   Subject: converting from maven1

Re: RE: RE: converting from maven1 to maven2, pom for third party jars?

[Dooing]

 The way local and remote repositories are different, for example:
 
 - Local snapshots are not saved with timestamp, remote snapshots are saved
 with timestamps. If you use a local repository as remote repository, maven
 can't tell if a SNAPSHOT has changed and won't download newer SNAPSHOTS.

So - in other words - if I didn't use any snapshots so far, there won't be 
differences and I could simply upload my local repo?!

Re-deploying every dependency MANUALLY would be VERY time consuming...
:-(

Thanks in advance,

Stefanie

-- 
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED]

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

converting from maven1 to maven2, pom for third party jars?

[David Delbecq]

Hello,

in the process of converting our app from maven1 to maven2, we changed 
our repository to have maven2 structure. For most library we use public 
repositories (maven, jboss, apache) to fetch files. But from some 
libraries we had to make them available to our local repository, moving 
the jar from his group/jars/artefact-version.jar to 
group/artifact/version/artifact-version.jar.


However, for the jar there is no pom files coming along, just a jar. 
maven2 has no special trouble handling them, except it keeps trying to 
go to all our configured repositories and try to download those 
inexistant pom:
Downloading: 
http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading: 
http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading: 
http://xxx/repository/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading: 
http://download.java.net/maven/2//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading: 
http://xxx/repository/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://download.java.net/maven/2//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
As you see, it tries to go to 5 different repositories, everytime to get 
a 404. Is there a recommended way to either


a) tell maven that there is definitely no pom to download
b) create the pom and metadata file from a .jar file (generic pom with 
correct names, but no dependencies)?
I tried for some jar to manually create pom, i received complains about 
checksums ? and maven ignored the file!


--
David Delbecq
Institut Royal Météorologique
Ext:557


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

RE: converting from maven1 to maven2, pom for third party jars?

[nicklist]

There is a solution for this problem. The deploy:deploy-file will automatically 
generate a pom file.

So, remove the jars from your remote repository and deploy them again with mvn 
deploy:deploy-file .

Perhaps if you make a list with the directories it should be possible to create 
a little script to do it.

Hth,

Nick S.


-Original Message-
From: David Delbecq [mailto:[EMAIL PROTECTED]
Sent: Wed 3/5/2008 16:27
To: Maven Users List
Subject: converting from maven1 to maven2, pom for third party jars?
 
Hello,

in the process of converting our app from maven1 to maven2, we changed 
our repository to have maven2 structure. For most library we use public 
repositories (maven, jboss, apache) to fetch files. But from some 
libraries we had to make them available to our local repository, moving 
the jar from his group/jars/artefact-version.jar to 
group/artifact/version/artifact-version.jar.

However, for the jar there is no pom files coming along, just a jar. 
maven2 has no special trouble handling them, except it keeps trying to 
go to all our configured repositories and try to download those 
inexistant pom:
 Downloading: 
 http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
 Downloading: 
 http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
 Downloading: 
 http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
 Downloading: 
 http://repository.jboss.com/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
 Downloading: 
 http://repo1.maven.org/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
 Downloading: 
 http://xxx/repository/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
 Downloading: 
 http://download.java.net/maven/2//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
 Downloading: 
 http://archiva.openqa.org/repository/releases//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
 Downloading: 
 http://repository.jboss.com/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
 Downloading: 
 http://repo1.maven.org/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
 Downloading: 
 http://xxx/repository/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
 Downloading: 
 http://download.java.net/maven/2//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
 Downloading: 
 http://archiva.openqa.org/repository/releases//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
 Downloading: 
 http://repository.jboss.com/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
 Downloading: 
 http://repo1.maven.org/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
As you see, it tries to go to 5 different repositories, everytime to get 
a 404. Is there a recommended way to either

a) tell maven that there is definitely no pom to download
b) create the pom and metadata file from a .jar file (generic pom with 
correct names, but no dependencies)?
I tried for some jar to manually create pom, i received complains about 
checksums ? and maven ignored the file!

-- 
David Delbecq
Institut Royal Météorologique
Ext:557


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

Re: converting from maven1 to maven2, pom for third party jars?

[delbd]

the deploy target doesnt seem to accept the fact our local repository 
requires password authentification. it just fails. Our server ask client 
for credential for write operation (apache DAV mod) but maven doesn't 
try with password. i'll give a try using install:install-file thanks




[EMAIL PROTECTED] a écrit :

There is a solution for this problem. The deploy:deploy-file will automatically 
generate a pom file.

So, remove the jars from your remote repository and deploy them again with mvn 
deploy:deploy-file .

Perhaps if you make a list with the directories it should be possible to create 
a little script to do it.

Hth,

Nick S.


-Original Message-
From: David Delbecq [mailto:[EMAIL PROTECTED]
Sent: Wed 3/5/2008 16:27
To: Maven Users List
Subject: converting from maven1 to maven2, pom for third party jars?
 
Hello,


in the process of converting our app from maven1 to maven2, we changed 
our repository to have maven2 structure. For most library we use public 
repositories (maven, jboss, apache) to fetch files. But from some 
libraries we had to make them available to our local repository, moving 
the jar from his group/jars/artefact-version.jar to 
group/artifact/version/artifact-version.jar.


However, for the jar there is no pom files coming along, just a jar. 
maven2 has no special trouble handling them, except it keeps trying to 
go to all our configured repositories and try to download those 
inexistant pom:
  
Downloading: 
http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading: 
http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading: 
http://xxx/repository/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading: 
http://download.java.net/maven/2//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading: 
http://xxx/repository/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://download.java.net/maven/2//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom

As you see, it tries to go to 5 different repositories, everytime to get 
a 404. Is there a recommended way to either


a) tell maven that there is definitely no pom to download
b) create the pom and metadata file from a .jar file (generic pom with 
correct names, but no dependencies)?
I tried for some jar to manually create pom, i received complains about 
checksums ? and maven ignored the file!


  



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

Re: converting from maven1 to maven2, pom for third party jars?

[Nick Stolwijk]

Take a look at the repositoryId [1] option of deploy-file and the server 
section in settings.xml [2]. They should take care of your authorisation.


Hth,

Nick Stolwijk

[1] 
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId
[2] 
http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_server


delbd wrote:
the deploy target doesnt seem to accept the fact our local repository 
requires password authentification. it just fails. Our server ask 
client for credential for write operation (apache DAV mod) but maven 
doesn't try with password. i'll give a try using install:install-file 
thanks




[EMAIL PROTECTED] a écrit :
There is a solution for this problem. The deploy:deploy-file will 
automatically generate a pom file.


So, remove the jars from your remote repository and deploy them again 
with mvn deploy:deploy-file .


Perhaps if you make a list with the directories it should be possible 
to create a little script to do it.


Hth,

Nick S.


-Original Message-
From: David Delbecq [mailto:[EMAIL PROTECTED]
Sent: Wed 3/5/2008 16:27
To: Maven Users List
Subject: converting from maven1 to maven2, pom for third party jars?
 
Hello,


in the process of converting our app from maven1 to maven2, we 
changed our repository to have maven2 structure. For most library we 
use public repositories (maven, jboss, apache) to fetch files. But 
from some libraries we had to make them available to our local 
repository, moving the jar from his group/jars/artefact-version.jar 
to group/artifact/version/artifact-version.jar.


However, for the jar there is no pom files coming along, just a 
jar. maven2 has no special trouble handling them, except it keeps 
trying to go to all our configured repositories and try to download 
those inexistant pom:
 
Downloading: 
http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://xxx/repository/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://download.java.net/maven/2//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://xxx/repository/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://download.java.net/maven/2//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom 

Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom 

Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom 

Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom

As you see, it tries to go to 5 different repositories, everytime to 
get a 404. Is there a recommended way to either


a) tell maven that there is definitely no pom to download
b) create the pom and metadata file from a .jar file (generic pom 
with correct names, but no dependencies)?
I tried for some jar to manually create pom, i received complains 
about checksums ? and maven ignored the file!


  



-
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: converting from maven1 to maven2, pom for third party jars?

[david delbecq]

Did :) does not work, will investigate further. For now am doing 
scripted convertion server side, attackign directly the server 
direcgtory structure using install-file, works like a charm :D


Nick Stolwijk a écrit :
Take a look at the repositoryId [1] option of deploy-file and the 
server section in settings.xml [2]. They should take care of your 
authorisation.


Hth,

Nick Stolwijk

[1] 
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId 

[2] 
http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_server 



delbd wrote:
the deploy target doesnt seem to accept the fact our local repository 
requires password authentification. it just fails. Our server ask 
client for credential for write operation (apache DAV mod) but maven 
doesn't try with password. i'll give a try using install:install-file 
thanks




[EMAIL PROTECTED] a écrit :
There is a solution for this problem. The deploy:deploy-file will 
automatically generate a pom file.


So, remove the jars from your remote repository and deploy them 
again with mvn deploy:deploy-file .


Perhaps if you make a list with the directories it should be 
possible to create a little script to do it.


Hth,

Nick S.


-Original Message-
From: David Delbecq [mailto:[EMAIL PROTECTED]
Sent: Wed 3/5/2008 16:27
To: Maven Users List
Subject: converting from maven1 to maven2, pom for third party jars?
 
Hello,


in the process of converting our app from maven1 to maven2, we 
changed our repository to have maven2 structure. For most library we 
use public repositories (maven, jboss, apache) to fetch files. But 
from some libraries we had to make them available to our local 
repository, moving the jar from his group/jars/artefact-version.jar 
to group/artifact/version/artifact-version.jar.


However, for the jar there is no pom files coming along, just a 
jar. maven2 has no special trouble handling them, except it keeps 
trying to go to all our configured repositories and try to download 
those inexistant pom:
 
Downloading: 
http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://xxx/repository/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://download.java.net/maven/2//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://xxx/repository/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://download.java.net/maven/2//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom 

Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom 

Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom 

Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom

As you see, it tries to go to 5 different repositories, everytime to 
get a 404. Is there a recommended way to either


a) tell maven that there is definitely no pom to download
b) create the pom and metadata file from a .jar file (generic pom 
with correct names, but no dependencies)?
I tried for some jar to manually create pom, i received complains 
about checksums ? and maven ignored the file!


  



-
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: converting from maven1 to maven2, pom for third party jars?

[Nick Stolwijk]

There are many problems with installing files into your remote 
repository, especially with the metadata and snapshots.


What I noticed with settings.xml. If you have a repository and a server 
with the same id, it will not pickup the credentials from the server. 
Most of the users with an own repository has a repository and a server 
part for the same repository. In this case use different id's (ie. 
repositoryId.server for the server).


Hth,

Nick S.

david delbecq wrote:
Did :) does not work, will investigate further. For now am doing 
scripted convertion server side, attackign directly the server 
direcgtory structure using install-file, works like a charm :D


Nick Stolwijk a écrit :
Take a look at the repositoryId [1] option of deploy-file and the 
server section in settings.xml [2]. They should take care of your 
authorisation.


Hth,

Nick Stolwijk

[1] 
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId 

[2] 
http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_server 



delbd wrote:
the deploy target doesnt seem to accept the fact our local 
repository requires password authentification. it just fails. Our 
server ask client for credential for write operation (apache DAV 
mod) but maven doesn't try with password. i'll give a try using 
install:install-file thanks




[EMAIL PROTECTED] a écrit :
There is a solution for this problem. The deploy:deploy-file will 
automatically generate a pom file.


So, remove the jars from your remote repository and deploy them 
again with mvn deploy:deploy-file .


Perhaps if you make a list with the directories it should be 
possible to create a little script to do it.


Hth,

Nick S.


-Original Message-
From: David Delbecq [mailto:[EMAIL PROTECTED]
Sent: Wed 3/5/2008 16:27
To: Maven Users List
Subject: converting from maven1 to maven2, pom for third party jars?
 
Hello,


in the process of converting our app from maven1 to maven2, we 
changed our repository to have maven2 structure. For most library 
we use public repositories (maven, jboss, apache) to fetch files. 
But from some libraries we had to make them available to our local 
repository, moving the jar from his group/jars/artefact-version.jar 
to group/artifact/version/artifact-version.jar.


However, for the jar there is no pom files coming along, just a 
jar. maven2 has no special trouble handling them, except it keeps 
trying to go to all our configured repositories and try to download 
those inexistant pom:
 
Downloading: 
http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom 

Downloading: 
http://xxx/repository/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://download.java.net/maven/2//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom 

Downloading: 
http://xxx/repository/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading: 
http://download.java.net/maven/2//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom 

Downloading: 
http://archiva.openqa.org/repository/releases//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom 

Downloading: 
http://repository.jboss.com/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom 

Downloading: 
http://repo1.maven.org/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom

As you see, it tries to go to 5 different repositories, everytime 
to get a 404. Is there a recommended way to either


a) tell maven that there is definitely no pom to download
b) create the pom and metadata file from a .jar file (generic pom 
with correct names, but no dependencies)?
I tried for some jar to manually create pom, i received complains 
about checksums ? and maven ignored the file!


  



-
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: converting from maven1 to maven2, pom for third party jars?

[Dooing]

To be able to deploy something on your company's remote server,
have a look at Distribution Management.

What I do for those external jars is - on the console, when maven doesn't find 
a depdency, it always gives you the exact String you need to use to install it 
on your local server or to deploy it on your company's remote server. I always 
copy this String from the console, then edit it in a text editor, put the jar 
in the same folder as the pom, add the name of the pom to the end of the 
String, hit enter, the jar gets installed, its poms and checksums created, when 
done, I delete the jar I put in the project's folder.

I've never tried the deploy option, as I am planning to copy my entire local 
repository to the remote one, as soon as I am finished migrating to Maven 2. 
The install version works perfectly (and I am sure when you set up distribution 
management, this works perfectly too).
To set up Distribution Management, Add it to your pom, then set the login 
information in your setting.xml, though I wouldn't recommend you to leave away 
the password - a) for security reasons b) so that noone can accidently upload 
something to your repository...

Hope that helps,

Christine
 Original-Nachricht 
 Datum: Wed, 05 Mar 2008 23:29:53 +0100
 Von: david delbecq [EMAIL PROTECTED]
 An: Maven Users List users@maven.apache.org
 Betreff: Re: converting from maven1 to maven2, pom for third party jars?

 Did :) does not work, will investigate further. For now am doing 
 scripted convertion server side, attackign directly the server 
 direcgtory structure using install-file, works like a charm :D
 
 Nick Stolwijk a écrit :
  Take a look at the repositoryId [1] option of deploy-file and the 
  server section in settings.xml [2]. They should take care of your 
  authorisation.
 
  Hth,
 
  Nick Stolwijk
 
  [1] 
 
 http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId
  
 
  [2] 
 
 http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_server 
 
 
  delbd wrote:
  the deploy target doesnt seem to accept the fact our local repository 
  requires password authentification. it just fails. Our server ask 
  client for credential for write operation (apache DAV mod) but maven 
  doesn't try with password. i'll give a try using install:install-file 
  thanks
 
 
 
  [EMAIL PROTECTED] a écrit :
  There is a solution for this problem. The deploy:deploy-file will 
  automatically generate a pom file.
 
  So, remove the jars from your remote repository and deploy them 
  again with mvn deploy:deploy-file .
 
  Perhaps if you make a list with the directories it should be 
  possible to create a little script to do it.
 
  Hth,
 
  Nick S.
 
 
  -Original Message-
  From: David Delbecq [mailto:[EMAIL PROTECTED]
  Sent: Wed 3/5/2008 16:27
  To: Maven Users List
  Subject: converting from maven1 to maven2, pom for third party jars?
   
  Hello,
 
  in the process of converting our app from maven1 to maven2, we 
  changed our repository to have maven2 structure. For most library we 
  use public repositories (maven, jboss, apache) to fetch files. But 
  from some libraries we had to make them available to our local 
  repository, moving the jar from his group/jars/artefact-version.jar 
  to group/artifact/version/artifact-version.jar.
 
  However, for the jar there is no pom files coming along, just a 
  jar. maven2 has no special trouble handling them, except it keeps 
  trying to go to all our configured repositories and try to download 
  those inexistant pom:
   
  Downloading: 
 
 http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
 
  Downloading: 
 
 http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
 
  Downloading: 
 
 http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
 
  Downloading: 
 
 http://repository.jboss.com/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
 
  Downloading: 
 
 http://repo1.maven.org/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
  
 
  Downloading: 
 
 http://xxx/repository/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
  
 
  Downloading: 
 
 http://download.java.net/maven/2//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
  
 
  Downloading: 
 
 http://archiva.openqa.org/repository/releases//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
  
 
  Downloading: 
 
 http://repository.jboss.com/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
  
 
  Downloading: 
 
 http://repo1.maven.org/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
  
 
  Downloading: 
  http://xxx/repository/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
  Downloading: 
 
 http://download.java.net/maven/2//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom 
 
  Downloading: 
 
 http://archiva.openqa.org/repository/releases//enhydra/dods/ejen

Re: accessing sources of third party jars

[Christian Goetze]

Edwin Punzalan wrote:



If the artifacts have sources and javadocs deployed with them, then 
using -DdownloadSources=true and -DdownloadJavadocs=true is what you 
need.  The plugin will download them and attach them to the project to 
help you in your development.


Hope that helps


^_^


Ok, and how are they deployed into the repo? What is the expected 
format/naming/location?

--
cg

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

Re: accessing sources of third party jars

[Christian Goetze]

Christian Goetze wrote:


Edwin Punzalan wrote:



If the artifacts have sources and javadocs deployed with them, then 
using -DdownloadSources=true and -DdownloadJavadocs=true is what you 
need.  The plugin will download them and attach them to the project 
to help you in your development.


Hope that helps


^_^



Ok, and how are they deployed into the repo? What is the expected 
format/naming/location?

--
cg


Answered the question myself: xyz-1.2.3-sources.jar and 
xyz-1.2.3-javadoc.jar -sigh- plural/singular mixup


Now, for the next trick: how can I cause these to be downloaded without 
regenerating the project files?

--
cg

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

accessing sources of third party jars

[Christian Goetze]

This is not clear for me from the maven book.

We have some third party jars that come with source code and javadocs, 
and I'd like those to be retrieved via a maven build. How can I do that? 
Do I actually need to make these into full-blown modules or is there a 
way to just handle the zip files directly, since idea is able to look at 
zip files for sources and javadocs...

--
cg

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

Re: accessing sources of third party jars

[Edwin Punzalan]

If the artifacts have sources and javadocs deployed with them, then 
using -DdownloadSources=true and -DdownloadJavadocs=true is what you 
need.  The plugin will download them and attach them to the project to 
help you in your development.


Hope that helps


^_^


Christian Goetze wrote:

This is not clear for me from the maven book.

We have some third party jars that come with source code and javadocs, 
and I'd like those to be retrieved via a maven build. How can I do 
that? Do I actually need to make these into full-blown modules or is 
there a way to just handle the zip files directly, since idea is able 
to look at zip files for sources and javadocs...

--
cg

-
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 several third party JARs to with one pom

[franz see]

Good day to you, Aaron,

If those are 3 maven projects that have to be always jar'd together, then
you might want to consider combining them all into one maven project. If
not, have a pom for each one of them. 

Cheers,
Franz


struberg wrote:
 
 Are those jars 3-rd party tools or selfmade jars?
 
 Anyway, i recommend using 3 poms. This is the only way
 of detecting/get rid of things like cyclic
 dependencies etc.
 
 lg,
 strub
 
 --- Wayne Fay [EMAIL PROTECTED] schrieb:
 
 No, unless you package the three Jars together as a
 single Jar (unjar
 all 3 into one directory which you then re-Jar).
 
 Wayne
 
 On 11/29/06, [EMAIL PROTECTED]
 [EMAIL PROTECTED] wrote:
  Hello,
 
  I have a fairly complex set of JARs (three) which
 belong together. I know
  how to deploy them to my site repository with a
 module project (one pom
  per JAR) but I was wondering if I could get away
 with just one pom.xml?
 
  Regards,
 
  --
  Aaron Digulla
 
 
 

 -
  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]
 
 
 
 
 
   
 ___ 
 Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Deploying-several-third-party-JARs-to-with-one-pom-tf2725177s177.html#a7623453
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Deploying several third party JARs to with one pom

[Aaron . Digulla]

Hello,

I have a fairly complex set of JARs (three) which belong together. I know 
how to deploy them to my site repository with a module project (one pom 
per JAR) but I was wondering if I could get away with just one pom.xml?

Regards,

-- 
Aaron Digulla


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

Re: Deploying several third party JARs to with one pom

[Wayne Fay]

No, unless you package the three Jars together as a single Jar (unjar
all 3 into one directory which you then re-Jar).

Wayne

On 11/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Hello,

I have a fairly complex set of JARs (three) which belong together. I know
how to deploy them to my site repository with a module project (one pom
per JAR) but I was wondering if I could get away with just one pom.xml?

Regards,

--
Aaron Digulla


-
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 several third party JARs to with one pom

[Mark Struberg]

Are those jars 3-rd party tools or selfmade jars?

Anyway, i recommend using 3 poms. This is the only way
of detecting/get rid of things like cyclic
dependencies etc.

lg,
strub

--- Wayne Fay [EMAIL PROTECTED] schrieb:

 No, unless you package the three Jars together as a
 single Jar (unjar
 all 3 into one directory which you then re-Jar).
 
 Wayne
 
 On 11/29/06, [EMAIL PROTECTED]
 [EMAIL PROTECTED] wrote:
  Hello,
 
  I have a fairly complex set of JARs (three) which
 belong together. I know
  how to deploy them to my site repository with a
 module project (one pom
  per JAR) but I was wondering if I could get away
 with just one pom.xml?
 
  Regards,
 
  --
  Aaron Digulla
 
 
 

-
  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]
 
 




___ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

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

Feature Request: Improved support for third party JARs

[Markus KARG]

Dear Maven Community,

currently Maven's support for third party JARs (i. e., JARs not built 
with Maven that do not have the version found in their file name) is 
problematic. If you have followed the FOP discussion lately happened in 
this list, you will understand that there is a need to improve Maven's 
support for JARs with Non-Mavenized-Names.


I have files a feature request with the JIRA system on Codehaus. If you 
are interested in this feature, please log in and vote for it.


Here is the URL: http://jira.codehaus.org/browse/MNG-2572

Thanks
Markus
begin:vcard
fn:Markus KARG
n:KARG;Markus
org:QUIPSY QUALITY GmbH;Entwicklung / R  D
adr:;;Stuttgarter Strasse 23;Pforzheim;Baden-Wuerttemberg;75179;Bundesrepublik Deutschland
email;internet:[EMAIL PROTECTED]
title:Staatl. gepr. Inf.
tel;work:+49-7231-9189-52
tel;fax:+49-7231-9189-59
note:QUIPSY(R) Entwicklung / R  D
x-mozilla-html:TRUE
url:http://www.quipsy.de
version:2.1
end:vcard



smime.p7s
Description: S/MIME Cryptographic Signature

Sharing third party jars in ibiblio

[Aleksei Valikov]

Hi folks,

I would like to share some third party jars in ibiblio. I've searched the docs - 
they describe how to install third party jars in a local repository and how to 
share own jars (built with maven) in ibiblio. The problem I have now is that I 
need to share the Compass Framework jars in some kind of a central repo 
(preferrably ibiblio). I have an allowance from Compass Framework project owner. 
Could anyone help me out?


Bye.
/lexi

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

Re: Sharing third party jars in ibiblio

[Allan Ramirez]

Please visit this guide

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

-allan

Aleksei Valikov wrote:

Hi folks,

I would like to share some third party jars in ibiblio. I've searched 
the docs - they describe how to install third party jars in a local 
repository and how to share own jars (built with maven) in ibiblio. 
The problem I have now is that I need to share the Compass Framework 
jars in some kind of a central repo (preferrably ibiblio). I have an 
allowance from Compass Framework project owner. Could anyone help me out?


Bye.
/lexi

-
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: Sharing third party jars in ibiblio

[Aleksei Valikov]

Hi.


Please visit this guide

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


Yes, I've seen it - but this guide assumes these are my artifacts, so there's 
pom.xml, directory structure etc. I have nothing like that, I just have a 
compass.jar file which I'd like to share under org.compass/compass/0.9.1.


Bye.
/lexi

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

Re: Sharing third party jars in ibiblio

[Tim Kettler]

Hi,

pastet from the guide:

--
If you are not using maven as your build system but want something uploaded to Ibiblio 
then you just need to make a JAR (using the jar executable, not zip, pkzip or equivalent) 
with the following format:


pom.xml
foo-1.0.jar (or whatever artifact is referred to in the pom.xml)
foo-1.0-sources.jar (optional, jar containing java sources)
foo-1.0-javadoc.jar (optional, jar containing javadocs)
--

If the project doesn't provide a pom you have to create one for the upload bundle 
yourself. Be sure it contains at least the following information (again pasted from the 
guide):


--
Note that the bundle will be read by a script, so it must follow the above format. Also, 
the pom.xml should at least contain the following elements:


* modelVersion
* groupId
* artifactId
* packaging
* name
* version
* url
* licenses
* scm url
* description
* dependencies
--

Hope this helps
-Tim

Aleksei Valikov schrieb:

Hi.


Please visit this guide

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


Yes, I've seen it - but this guide assumes these are my artifacts, so 
there's pom.xml, directory structure etc. I have nothing like that, I 
just have a compass.jar file which I'd like to share under 
org.compass/compass/0.9.1.


Bye.
/lexi

-
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]

third party jars in local repository only

[Fabien Benoit]

Hello,

I'm using Maven 2.0.4 and i have trouble in building a local repository.

After having installed some third party jars to my local repository,
using...

mvn install:install-file -Dfile=path-to-file -DgroupId=group-id \
   -DartifactId=artifact-id -Dversion=version -Dpackaging=packaging

...the correct directories are created and the jar is copied but I've
noticed that no POMs file
are created (do I have to create them manually, to declare their transitive
dependencies?).
In addition maven tries to download then from ibiblio each time I run a
compilation (and
of course it fails to find them). But the compilation is successful.

Btw, these jars comes from the Jboss application server (ejbs API and web
services).

Do I need a true remote repository, referenced in settings.xml ? Or is a
local repository sufficient
for playing with third party jars ?

Thanks.

Re: third party jars in local repository only

[Alexandre Poitras]

I think it's because you forgot -DgeneratePom=true. Should fix the
problem. Or you can always write the pom by hand if you need to
specify some transitive dependencies and specify it using
-DpomFile=mypom. It's more work but more reliable :)

Another advice, keep a fresh copy of your files or use an internal
corporate repository because it's hard to remember exactly what you
have installed in there and so what you need to start building your
project on another desktop.

Hope it's help!

On 5/18/06, Fabien Benoit [EMAIL PROTECTED] wrote:

Hello,

I'm using Maven 2.0.4 and i have trouble in building a local repository.

After having installed some third party jars to my local repository,
using...

mvn install:install-file -Dfile=path-to-file -DgroupId=group-id \
-DartifactId=artifact-id -Dversion=version -Dpackaging=packaging

...the correct directories are created and the jar is copied but I've
noticed that no POMs file
are created (do I have to create them manually, to declare their transitive
dependencies?).
In addition maven tries to download then from ibiblio each time I run a
compilation (and
of course it fails to find them). But the compilation is successful.

Btw, these jars comes from the Jboss application server (ejbs API and web
services).

Do I need a true remote repository, referenced in settings.xml ? Or is a
local repository sufficient
for playing with third party jars ?

Thanks.




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

expressing dependencies of third-party jars in internal repository

[Doug Douglass]

Specifically, I'm in the process of placing all the appropriate jars 
from Suns Web Services Dev Pack into our internal maven repo. But how 
should dependencies for these jars be expressed?

For example, the JWSDP 1.5 contains jaxp-api.jar (1.2.6_01), which 
depends on SAX 2.0, which in turn is available via the ibiblio maven 
repo (sax-2.0.1.jar). Even if I chose to place sax-2.0.jar into our 
internal maven repo, is there a way to know that jaxp-api-1.2.6_01.jar 
is dependent upon sax-2.0.jar (or sax-2.0.1.jar)? Should I be creating a 
POM for JAXP, then perhaps use a tool like Deputy (search the archives) 
to discover the dependecies.

Just looking for some advice on best practices...
TIA,
Doug
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: expressing dependencies of third-party jars in internal repository

[Matthias Burbach]

Hi,

The other day I posted a similar question.

It was in reply to Brett's hint that the Deputy sources don't build
because I defined dependencies to 3rd party jars which are only
available in my local repository under exactly those names.

The question went like this:
...
I am not so sure, however, what to do about the 'doesn't build'
problem. The obvious thing would be, of course, not to use a
private-only repository for the dependencies. The problem then is: The
jars I use are mainly taken from the JDOM distribution and I don't know
if I can find exactly those anywhere out there in a public repository.
And even worse, they seldom have a proper version coded in the file
name nor do they have a POM stating their dependencies. Same thing with
the Java Help jar. So I renamed jars to include versions I figured from
Mainfest files and I 'invented' a few POMs and put all of this into my
private repository.

How can I do better? Is there an accepted way to improve the contents
of a public repository even if it concerns artifacts I'm just a user
of?
...

It would be great to find a better solution to this.

Regards,
Matthias


-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im
Auftrag von Doug Douglass
Gesendet: Mittwoch, 4. Mai 2005 21:27
An: Maven Users List
Betreff: expressing dependencies of third-party jars in internal
repository

Specifically, I'm in the process of placing all the appropriate jars 
from Suns Web Services Dev Pack into our internal maven repo. But how 
should dependencies for these jars be expressed?

For example, the JWSDP 1.5 contains jaxp-api.jar (1.2.6_01), which 
depends on SAX 2.0, which in turn is available via the ibiblio maven 
repo (sax-2.0.1.jar). Even if I chose to place sax-2.0.jar into our 
internal maven repo, is there a way to know that jaxp-api-1.2.6_01.jar

is dependent upon sax-2.0.jar (or sax-2.0.1.jar)? Should I be creating a

POM for JAXP, then perhaps use a tool like Deputy (search the archives) 
to discover the dependecies.

Just looking for some advice on best practices...

TIA,
Doug

-
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: AW: expressing dependencies of third-party jars in internal repository

[Doug Douglass]

Matthias,
This issue was the initial reason I setup an internal repo -- I couldn't 
determine the EXACT versions of the dependencies required by/bundled 
with a third party jar, so I did just I as you describe below.

The general problem, as you know, is discovering the dependencies of a 
dependency and having them all added to a projects POM (or at least it's 
classpath). I presume this is where Deputy helps (I haven't had time yet 
to check it out).

Perhaps a new bundle dependency type could be used (i.e., 
groupdId/bundles/artifactId-version...) where the bundle is just a 
zip of jars. Or better yet a jar with a Class-Path entry in its 
manifest. H...

Since I haven't written any plugins (yet), I'm not sure of the 
feasibility/effort of adding a new dependency type, but I'm willing to 
help ;)

Cheers,
Doug
Matthias Burbach wrote:
Hi,
The other day I posted a similar question.
It was in reply to Brett's hint that the Deputy sources don't build
because I defined dependencies to 3rd party jars which are only
available in my local repository under exactly those names.
The question went like this:
...
I am not so sure, however, what to do about the 'doesn't build'
problem. The obvious thing would be, of course, not to use a
private-only repository for the dependencies. The problem then is: The
jars I use are mainly taken from the JDOM distribution and I don't know
if I can find exactly those anywhere out there in a public repository.
And even worse, they seldom have a proper version coded in the file
name nor do they have a POM stating their dependencies. Same thing with
the Java Help jar. So I renamed jars to include versions I figured from
Mainfest files and I 'invented' a few POMs and put all of this into my
private repository.
How can I do better? Is there an accepted way to improve the contents
of a public repository even if it concerns artifacts I'm just a user
of?
...

It would be great to find a better solution to this.
Regards,
Matthias

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

AW: AW: expressing dependencies of third-party jars in internal repository

[Matthias Burbach]

Doug,

You're right that Deputy recursively discovers dependencies of
dependencies and adds them to a project's POM.
The prerequisite to make this work is that each dependency project has a
POM in a repository which defines its dependencies.
And this is where the problem is: if 3rd-party jars occur somewhere in
my dependency graph which are not (yet) represented by a proper POM in a
public repository I have to reconstruct/fake it in my local repository.
But this is not in line with the Maven idea as I understand it (though
it works in an isolated environment).

Cheers,
Matthias

-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im
Auftrag von Doug Douglass
Gesendet: Donnerstag, 5. Mai 2005 00:06
An: Maven Users List
Betreff: Re: AW: expressing dependencies of third-party jars in internal
repository

Matthias,

This issue was the initial reason I setup an internal repo -- I couldn't

determine the EXACT versions of the dependencies required by/bundled 
with a third party jar, so I did just I as you describe below.

The general problem, as you know, is discovering the dependencies of a 
dependency and having them all added to a projects POM (or at least it's

classpath). I presume this is where Deputy helps (I haven't had time yet

to check it out).

Perhaps a new bundle dependency type could be used (i.e., 
groupdId/bundles/artifactId-version...) where the bundle is just a

zip of jars. Or better yet a jar with a Class-Path entry in its 
manifest. H...

Since I haven't written any plugins (yet), I'm not sure of the 
feasibility/effort of adding a new dependency type, but I'm willing to 
help ;)

Cheers,
Doug

Matthias Burbach wrote:
 Hi,
 
 The other day I posted a similar question.
 
 It was in reply to Brett's hint that the Deputy sources don't build
 because I defined dependencies to 3rd party jars which are only
 available in my local repository under exactly those names.
 
 The question went like this:
 
...
I am not so sure, however, what to do about the 'doesn't build'
 
 problem. The obvious thing would be, of course, not to use a
 private-only repository for the dependencies. The problem then is:
The
 jars I use are mainly taken from the JDOM distribution and I don't
know
 if I can find exactly those anywhere out there in a public
repository.
 And even worse, they seldom have a proper version coded in the file
 name nor do they have a POM stating their dependencies. Same thing
with
 the Java Help jar. So I renamed jars to include versions I figured
from
 Mainfest files and I 'invented' a few POMs and put all of this into
my
 private repository.
 
How can I do better? Is there an accepted way to improve the contents
 
 of a public repository even if it concerns artifacts I'm just a user
 of?
 
...
 
 
 It would be great to find a better solution to this.
 
 Regards,
 Matthias
 


-
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: AW: expressing dependencies of third-party jars in internal repository

[Brett Porter]

The plan going forward is for Maven 2.0 to support reading POMs for
these, but not distributing the JARs, so the error messages can be
more helpful. A plugin will be provided to make it easy to add to your
local/internal repository from a filesystem location.

HTH,
BRett

On 5/5/05, Matthias Burbach [EMAIL PROTECTED] wrote:
 Doug,
 
 You're right that Deputy recursively discovers dependencies of
 dependencies and adds them to a project's POM.
 The prerequisite to make this work is that each dependency project has a
 POM in a repository which defines its dependencies.
 And this is where the problem is: if 3rd-party jars occur somewhere in
 my dependency graph which are not (yet) represented by a proper POM in a
 public repository I have to reconstruct/fake it in my local repository.
 But this is not in line with the Maven idea as I understand it (though
 it works in an isolated environment).
 
 Cheers,
 Matthias
 
 -Ursprüngliche Nachricht-
 Von: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Im
 Auftrag von Doug Douglass
 Gesendet: Donnerstag, 5. Mai 2005 00:06
 An: Maven Users List
 Betreff: Re: AW: expressing dependencies of third-party jars in internal
 repository
 
 Matthias,
 
 This issue was the initial reason I setup an internal repo -- I couldn't
 
 determine the EXACT versions of the dependencies required by/bundled
 with a third party jar, so I did just I as you describe below.
 
 The general problem, as you know, is discovering the dependencies of a
 dependency and having them all added to a projects POM (or at least it's
 
 classpath). I presume this is where Deputy helps (I haven't had time yet
 
 to check it out).
 
 Perhaps a new bundle dependency type could be used (i.e.,
 groupdId/bundles/artifactId-version...) where the bundle is just a
 
 zip of jars. Or better yet a jar with a Class-Path entry in its
 manifest. H...
 
 Since I haven't written any plugins (yet), I'm not sure of the
 feasibility/effort of adding a new dependency type, but I'm willing to
 help ;)
 
 Cheers,
 Doug
 
 Matthias Burbach wrote:
  Hi,
 
  The other day I posted a similar question.
 
  It was in reply to Brett's hint that the Deputy sources don't build
  because I defined dependencies to 3rd party jars which are only
  available in my local repository under exactly those names.
 
  The question went like this:
 
 ...
 I am not so sure, however, what to do about the 'doesn't build'
 
  problem. The obvious thing would be, of course, not to use a
  private-only repository for the dependencies. The problem then is:
 The
  jars I use are mainly taken from the JDOM distribution and I don't
 know
  if I can find exactly those anywhere out there in a public
 repository.
  And even worse, they seldom have a proper version coded in the file
  name nor do they have a POM stating their dependencies. Same thing
 with
  the Java Help jar. So I renamed jars to include versions I figured
 from
  Mainfest files and I 'invented' a few POMs and put all of this into
 my
  private repository.
 
 How can I do better? Is there an accepted way to improve the contents
 
  of a public repository even if it concerns artifacts I'm just a user
  of?
 
 ...
 
 
  It would be great to find a better solution to this.
 
  Regards,
  Matthias
 
 
 -
 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]