Re: RE: including source in jar

[aok123]

Not a bad idea to have a reference to the source somewhere but I like a URL rather 
than a path.  At one time I thought about this in relation to build 
systems which may use the dependency information to build and rebuild 
the dependent artifact if need be.

> 
> From: "Eric Pugh" <[EMAIL PROTECTED]>
> Date: 2003/11/11 Tue AM 06:48:38 EST
> To: "'Maven Users List'" <[EMAIL PROTECTED]>
> Subject: RE: including source in jar
> 
> I like the idea of including src etc in the jar..  However, we should also
> think about how to work with non Maven jars..  Is there any sense to to
> adding something to the Eclipse plugin that allows you to define where to
> get src from?
> 
> For instance, I keep the source for OSWorkflow, and Ant built project, on
> c:\java\oswf\src\java..  So, would it make sense to have an .xml file that
> maps  the groupId/artifactID to a location?
> 
> 
> opensymphony
> osworkflow-2.6-dev
> c:\java\oswf\src\java
> 
> 
> This would at least obviate the need to change a whole bunch of things...
> Of course, every user is maintaining their own source...
> 
> Eric
> 
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Monday, November 10, 2003 12:43 AM
> > To: Maven Users List
> > Subject: Re: including source in jar
> >
> >
> > Building a debug vs non-debug jar does sound like a good idea.
> > --
> > dIon Gillard, Multitask Consulting
> > Blog:  http://blogs.codehaus.org/people/dion/
> > Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
> >
> >
> > Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> wrote
> > on 10/11/2003
> > 03:38:49 AM:
> >
> > > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2003-11-09 06:50]:
> > > > Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> wrote on
> > 09/11/2003
> > > > 12:45:46 PM:
> > > >
> > > > > * Vikas Phonsa <[EMAIL PROTECTED]> [2003-11-07 21:19]:
> > > > > > Can I have the jar goal generate a jar that includes
> > the source
> > code
> > > > file
> > > > > > also beside the .class files.
> > > > >
> > > > > I've been asking about creating separate debug and release build
> > > > > targets for some time now. A debug target would have a
> > source jar.
> > > > > This would make is easy to deploy the artifacts for use with
> > > > > Eclipse.
> > >
> > > > where did we get with this?
> > > >
> > > > Last I remember, my suggest was to use the dist plugin,
> > not the jar
> > > > plugin.
> > >
> > > I will start working on it this week. It just seems to me that Maven
> > > ought to support the two inevitable output paths, debug and release,
> > > but after reading through java, jar, and dist, I'll be able to
> > > better comment.
> > >
> > > --
> > > Alain Javier Guarnieri del Gesu - [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]
> 
> 


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

Re: Re: Usability issues & general ranting

[aok123]

> > I've basically given up on Maven for the time being. My impression
> > of the state of the project is that it should not be in beta, the
> > quality is more like that of an alpha-status project.
> Taken with the grain of salt it deserves.

I just recently switched to Maven and had many problems in the begining however in 
hind site the problems were mostly my fault.  At first I jumped to conclusions often 
pointing the finger at Maven.  I tried to be patient. I tried to be open to some of 
the new concepts it introduces.  Maven is a natural progression from Ant and looking 
back I realized that I was extremely narrow minded in my criticism.  

There are reasons why Maven does what it does.  It takes a bit of time to let these 
concepts sink in.  Its very hard to unlearn things like the $prj.home/lib directory 
thing and storing versionless jars in CVS.

Maven has expanded my horizons and I see it as a valuable tool.  After benefiting 
already from the versioned jars I came to respect Mavens refusal to allow me to 
continue.  In the end an early panic on my development machine saved me days of 
trouble in production.

There are concrete reasons behind Maven's operation and I'm sure you'll realize the 
why with time. You just need to take a couple of breaths and have faith.  Take it from 
a staunch Ant junky that switched to Maven.

Alex


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

Controling dependency timeouts

[aok123]

Hello, 
 
Is there a way to control dependency downloads timeouts from a remote 
repository when multiple repositories are used?  Would there be properties 
that can be put into the project.properties file for these settings? 
 
Thanks, 
Alex 


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