[m2] Maven2 artifact type question

[Mykel Alvis <my...@gmail.com>]

I apologize for not R'ing the F'ing Site, but I really don't have time
to delve too deeply into maven2 since I'm in midstream of making my
current maven1 projects work the way my manager wants them to.

A couple of members of my dev team have asked me a quesiton that I
can't easily answer.

In maven2, is it possible to specify a compile-time dependecy on a
source distribution for integration into a source debugger?

If that wasn't a good question, let me place it in terms of how we work now:
1. Our main (web) project depends on a jar built internally.  We
primarly use a SNAPSHOT of that jar since it's very volatile.
2. We use the mavenide and Eclipse, so we have the ability to attach
sources to our synchronized dependent jars for source debugging.
3. The dependent jar developer does a source distro when he does a
snapshot deploy.
4. During debug, the developer is forced to download (manually) a
snapshot source so that he's source debugging the same code that he's
running.
5. IF the source was listed as a dependecy, then it could
automagically appear in the repository, we could point a path variable
to it, and the mavenide code could be updated to preserve that link
for snapshots on a pom synchronize.

Will this be a possibility/reality with maven2 or am I asking too
much?  It doesn't seem like an edge case at all, since this question
has been asked by essentially every developer and technical manager at
every job I've worked where I've promoted maven.

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

Re: [m2] Maven2 artifact type question

[Ralph Pöllath <li...@poellath.org>]

Please make source and javadoc uploads the default.

Cheers,
-Ralph.

On 15.04.2005, at 01:13, Brett Porter wrote:
> Yes, Maven2 intends to provide source and javadoc uploads. I haven't
> decided if this should be on by default or not, but it will be trivial
> to enable if not.
>
> - Brett


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

Re: [m2] Maven2 artifact type question

[Milos Kleint <mk...@gmail.com>]

please make it part of default distribution, it's also trivial now to
upload javadocs but obviously noone does. For easy maven+ide
integration this is one of the key features. having a dependency
autmatically downloaded is just part of the story. in the IDE you want
to see the docs and want to browse the source (for example when
debugging or profiling).

Milos

On 4/15/05, Brett Porter <br...@gmail.com> wrote:
> Yes, Maven2 intends to provide source and javadoc uploads. I haven't
> decided if this should be on by default or not, but it will be trivial
> to enable if not.
> 
> - Brett
>

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

Re: [m2] Maven2 artifact type question

[Brett Porter <br...@gmail.com>]

Yes, Maven2 intends to provide source and javadoc uploads. I haven't
decided if this should be on by default or not, but it will be trivial
to enable if not.

- Brett

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

Re: [m2] Maven2 artifact type question

[Milos Kleint <mk...@gmail.com>]

If I understand the problem correctly, you want access to source (and
possibly javadoc) jars/zips of the dependency. That's crutial in the
IDE when debugging or for proper code completion.
 
Not sure if it's necessary to specify the link to the source in the
maven pom. It should be possible to do just by mevenide (since it
doesn't really make sense for the command line maven running on a
server for example). I've implemented that lately for mevenide
(netbeans integration). For any given dependency it allows the user to
check the remote repositories if javadoc or source is present.
However in 99.9% percent of the public dependencies it's not there.
I've blogged about it here.
http://blogs.codehaus.org/people/mkleint/archives/001024_maven_unused_features.html

My point is that the downloading part can be done by IDE integrations
by there needs to be some kind of process to encourage the population
of remote repositories with these source+javadoc artifacts.. I hope M2
improves the process, because in M1 javadoc:upload was not called at
all and there was not a goal for creating a source zip/jar that can be
used for IDE for debugging purposes easily. (i've created that goal
and submitted to the dist plugin -
http://jira.codehaus.org/browse/MPDIST-21)

Regards  


Milos Kleint
On 4/14/05, Mykel Alvis <my...@gmail.com> wrote:
> I apologize for not R'ing the F'ing Site, but I really don't have time
> to delve too deeply into maven2 since I'm in midstream of making my
> current maven1 projects work the way my manager wants them to.
> 
> A couple of members of my dev team have asked me a quesiton that I
> can't easily answer.
> 
> In maven2, is it possible to specify a compile-time dependecy on a
> source distribution for integration into a source debugger?
> 
> If that wasn't a good question, let me place it in terms of how we work now:
> 1. Our main (web) project depends on a jar built internally.  We
> primarly use a SNAPSHOT of that jar since it's very volatile.
> 2. We use the mavenide and Eclipse, so we have the ability to attach
> sources to our synchronized dependent jars for source debugging.
> 3. The dependent jar developer does a source distro when he does a
> snapshot deploy.
> 4. During debug, the developer is forced to download (manually) a
> snapshot source so that he's source debugging the same code that he's
> running.
> 5. IF the source was listed as a dependecy, then it could
> automagically appear in the repository, we could point a path variable
> to it, and the mavenide code could be updated to preserve that link
> for snapshots on a pom synchronize.
> 
> Will this be a possibility/reality with maven2 or am I asking too
> much?  It doesn't seem like an edge case at all, since this question
> has been asked by essentially every developer and technical manager at
> every job I've worked where I've promoted maven.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
>

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