Re: creating and using source archive
I created a new feature request in the JIRA instance for Maven 2 (http://jira.codehaus.org/browse/MNG-2248). You guys can add comments to it if you want to. This is the first time I've created a JIRA log so I hope I did it right. On 4/27/06, Wayne Fay <[EMAIL PROTECTED]> wrote: Discussions like these are great, but please make sure they result in a JIRA Enhancement request (or two) so the Maven Dev group can track, discuss, and perhaps even implement them. Otherwise the issues raised in these conversations will never be addressed. And I'll generally agree that sources and javadocs should be grabbed when they are available, with configuration available to disable this functionality, or vice-versa. Wayne On 4/27/06, jdigger <[EMAIL PROTECTED]> wrote: > > I agree with both Jamie and Aaron -- getting the sources and/or javadocs if > they are available should definately be a part of the standard "grab" that > downloading from a repository should do. > > -Jim Moore > > > Aaron Freeman wrote: > > > > I agree with Jamie. Since the ability to build javadoc and source jars > > is a built in part of the maven deploy plugin, it doesn't make sense > > that the only way to get maven to download them is using an eclipse > > specific plugin. What if people want to use these source files for > > other things or with other editors (like IDEA or NetBeans), then this > > functionality would have to be reimplemented. So, just as Jamie said, > > I think the piece that downloads the POMs and binaries should have a > > switch that will make it download the sources and javadocs (in the XML > > or as a -D option like on the eclipse plugin). > > > -- > View this message in context: http://www.nabble.com/creating-and-using-source-archive-t1512274.html#a4121026 > Sent from the Maven - Users forum at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating and using source archive
I don't really agree that downloading sources&javadoc should be standard, but I do think it should be possible. I hacked the eclipse plugin into something that can download sources&javadocs on demand for the dependencies of a given project and will upload it to JIRA tomorrow. Tom On 4/27/06, jdigger <[EMAIL PROTECTED]> wrote: I agree with both Jamie and Aaron -- getting the sources and/or javadocs if they are available should definately be a part of the standard "grab" that downloading from a repository should do. -Jim Moore Aaron Freeman wrote: > > I agree with Jamie. Since the ability to build javadoc and source jars > is a built in part of the maven deploy plugin, it doesn't make sense > that the only way to get maven to download them is using an eclipse > specific plugin. What if people want to use these source files for > other things or with other editors (like IDEA or NetBeans), then this > functionality would have to be reimplemented. So, just as Jamie said, > I think the piece that downloads the POMs and binaries should have a > switch that will make it download the sources and javadocs (in the XML > or as a -D option like on the eclipse plugin). > -- View this message in context: http://www.nabble.com/creating-and-using-source-archive-t1512274.html#a4121026 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating and using source archive
Discussions like these are great, but please make sure they result in a JIRA Enhancement request (or two) so the Maven Dev group can track, discuss, and perhaps even implement them. Otherwise the issues raised in these conversations will never be addressed. And I'll generally agree that sources and javadocs should be grabbed when they are available, with configuration available to disable this functionality, or vice-versa. Wayne On 4/27/06, jdigger <[EMAIL PROTECTED]> wrote: > > I agree with both Jamie and Aaron -- getting the sources and/or javadocs if > they are available should definately be a part of the standard "grab" that > downloading from a repository should do. > > -Jim Moore > > > Aaron Freeman wrote: > > > > I agree with Jamie. Since the ability to build javadoc and source jars > > is a built in part of the maven deploy plugin, it doesn't make sense > > that the only way to get maven to download them is using an eclipse > > specific plugin. What if people want to use these source files for > > other things or with other editors (like IDEA or NetBeans), then this > > functionality would have to be reimplemented. So, just as Jamie said, > > I think the piece that downloads the POMs and binaries should have a > > switch that will make it download the sources and javadocs (in the XML > > or as a -D option like on the eclipse plugin). > > > -- > View this message in context: > http://www.nabble.com/creating-and-using-source-archive-t1512274.html#a4121026 > Sent from the Maven - Users forum at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: creating and using source archive
I agree with both Jamie and Aaron -- getting the sources and/or javadocs if they are available should definately be a part of the standard "grab" that downloading from a repository should do. -Jim Moore Aaron Freeman wrote: > > I agree with Jamie. Since the ability to build javadoc and source jars > is a built in part of the maven deploy plugin, it doesn't make sense > that the only way to get maven to download them is using an eclipse > specific plugin. What if people want to use these source files for > other things or with other editors (like IDEA or NetBeans), then this > functionality would have to be reimplemented. So, just as Jamie said, > I think the piece that downloads the POMs and binaries should have a > switch that will make it download the sources and javadocs (in the XML > or as a -D option like on the eclipse plugin). > -- View this message in context: http://www.nabble.com/creating-and-using-source-archive-t1512274.html#a4121026 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating and using source archive
I agree with Jamie. Since the ability to build javadoc and source jars is a built in part of the maven deploy plugin, it doesn't make sense that the only way to get maven to download them is using an eclipse specific plugin. What if people want to use these source files for other things or with other editors (like IDEA or NetBeans), then this functionality would have to be reimplemented. So, just as Jamie said, I think the piece that downloads the POMs and binaries should have a switch that will make it download the sources and javadocs (in the XML or as a -D option like on the eclipse plugin). On 4/26/06, Jamie Bisotti <[EMAIL PROTECTED]> wrote: > On 4/26/06, Aaron Freeman <[EMAIL PROTECTED]> wrote: > > > > So what you all are saying is that the "eclipse:eclipse > > -DdownloadSources=true" command is the only way to get Maven to copy > > source jars into the local repository. So if you already have .project > > and .classpath file, the there is no way to get the sources in the > > local repository without messing up my .project and .classpath file. > > > > > > > > On 4/26/06, gdub <[EMAIL PROTECTED]> wrote: > > > Tom Huybrechts wrote: > > > > The Eclipse plugin will (or should) > > > > only download javadocs if the > > > > sources are not available. Makes > > > > sense for Eclipse, since it will > > > > extract the javadocs from the sources if needed. > > > > > > Ah. I see. I deleted a source > > > archive and it did indeed attach > > > the javadoc archive instead. > > > > > > However, I think it should attach > > > both if if finds them. In Eclipse, > > > shift-f2 pops up a browser pointed > > > at the javadocs for the item under > > > the cursor. If only the sources > > > are attached that function doesn't > > > work. > > > > > > With only the sources attached, > > > hovering over an item shows the javadoc > > > in a local window but the ui is not > > > as functional as the normal browser- > > > based api docs. > > > > > > -dub > > > > > > > > > - > > > 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] > > > > > Seems like there should be a non-Eclipse-related method of downloading > source/javadoc. I'd think whatever code downloads the POMs/binaries/etc > could/should be responsible for downloading these as well, at the same > time. Some sort of switch in the XML could turn this on/off for users who > don't like the default. > > My $0.02. > > -- > Jamie > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating and using source archive
Jamie Bisotti wrote: On 4/26/06, Aaron Freeman <[EMAIL PROTECTED]> wrote: So what you all are saying is that the "eclipse:eclipse -DdownloadSources=true" command is the only way to get Maven to copy source jars into the local repository. So if you already have .project and .classpath file, the there is no way to get the sources in the local repository without messing up my .project and .classpath file. I think that is correct. In browsing mail archives and Jira reports, I get the impression that the eclipse plugin is the reason that source archives exist in the repositories at all. Of course, now that sources might start to show up in the repositories, it opens up all kinds of interesting possibilities. For instance, the facility could be used to create a complete javadoc site for a project and all of its dependencies with near-zero configuration. Similarly, for jobs that require available 3rd-party source code be delivered with the system, having those sources--tied to exact releases--available in a repo could help ease the pain of "operation shrinkwrap" (as a colleague used to call it). -dub - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating and using source archive
On 4/26/06, Aaron Freeman <[EMAIL PROTECTED]> wrote: > > So what you all are saying is that the "eclipse:eclipse > -DdownloadSources=true" command is the only way to get Maven to copy > source jars into the local repository. So if you already have .project > and .classpath file, the there is no way to get the sources in the > local repository without messing up my .project and .classpath file. > > > > On 4/26/06, gdub <[EMAIL PROTECTED]> wrote: > > Tom Huybrechts wrote: > > > The Eclipse plugin will (or should) > > > only download javadocs if the > > > sources are not available. Makes > > > sense for Eclipse, since it will > > > extract the javadocs from the sources if needed. > > > > Ah. I see. I deleted a source > > archive and it did indeed attach > > the javadoc archive instead. > > > > However, I think it should attach > > both if if finds them. In Eclipse, > > shift-f2 pops up a browser pointed > > at the javadocs for the item under > > the cursor. If only the sources > > are attached that function doesn't > > work. > > > > With only the sources attached, > > hovering over an item shows the javadoc > > in a local window but the ui is not > > as functional as the normal browser- > > based api docs. > > > > -dub > > > > > > - > > 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] > > Seems like there should be a non-Eclipse-related method of downloading source/javadoc. I'd think whatever code downloads the POMs/binaries/etc could/should be responsible for downloading these as well, at the same time. Some sort of switch in the XML could turn this on/off for users who don't like the default. My $0.02. -- Jamie
Re: creating and using source archive
So what you all are saying is that the "eclipse:eclipse -DdownloadSources=true" command is the only way to get Maven to copy source jars into the local repository. So if you already have .project and .classpath file, the there is no way to get the sources in the local repository without messing up my .project and .classpath file. On 4/26/06, gdub <[EMAIL PROTECTED]> wrote: > Tom Huybrechts wrote: > > The Eclipse plugin will (or should) > > only download javadocs if the > > sources are not available. Makes > > sense for Eclipse, since it will > > extract the javadocs from the sources if needed. > > Ah. I see. I deleted a source > archive and it did indeed attach > the javadoc archive instead. > > However, I think it should attach > both if if finds them. In Eclipse, > shift-f2 pops up a browser pointed > at the javadocs for the item under > the cursor. If only the sources > are attached that function doesn't > work. > > With only the sources attached, > hovering over an item shows the javadoc > in a local window but the ui is not > as functional as the normal browser- > based api docs. > > -dub > > > - > 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: creating and using source archive
Tom Huybrechts wrote: > The Eclipse plugin will (or should) > only download javadocs if the > sources are not available. Makes > sense for Eclipse, since it will > extract the javadocs from the sources if needed. Ah. I see. I deleted a source archive and it did indeed attach the javadoc archive instead. However, I think it should attach both if if finds them. In Eclipse, shift-f2 pops up a browser pointed at the javadocs for the item under the cursor. If only the sources are attached that function doesn't work. With only the sources attached, hovering over an item shows the javadoc in a local window but the ui is not as functional as the normal browser- based api docs. -dub - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating and using source archive
The Eclipse plugin will (or should) only download javadocs if the sources are not available. Makes sense for Eclipse, since it will extract the javadocs from the sources if needed. Tom On 4/26/06, gdub <[EMAIL PROTECTED]> wrote: > gdub wrote: > > gdub wrote: > > I have the source and > > javadoc archives going into the > > repository just fine but the eclipse > > plugin isn't picking them up when I > > execute the eclipse:eclipse goal. > > It was just a plugin version issue. The > newest version picks up the sources just > fine. > > It does not set the javadoc archive, > though. Is that functionality supported > by the plugin? > >-dub > > - > 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: creating and using source archive
Tom Huybrechts wrote: If you execute 'mvn eclipse:eclipse -DdownloadSources=true', an Eclipse project will be generated with sources or javadocs attached. Thanks, Tom. I've started using that flag. However, a surprising number of packages on ibiblio don't include source or javadoc archives. I've resorted to packaging up those jars manually and copying them directly to the local repo. If we ever get our act together and set up a workgroup repository that effort won't have to be duplicated on every workstation. -dub - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating and using source archive
gdub wrote: Jake Pezaro wrote: > to get the source into your > repository then you need to > attache the source plugin > to the package phase as below. > this will then automatically > generate the sources and > deploy them. Wow, that was easy. That's going to save alot of time. Thank you. -dub Now the other side of the equation isn't working. I have the source and javadoc archives going into the repository just fine but the eclipse plugin isn't picking them up when I execute the eclipse:eclipse goal. I tried using -DeclipseDownloadSources=true but that didn't help. Is there another option I need to specify? -dub - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating and using source archive
gdub wrote: gdub wrote: I have the source and javadoc archives going into the repository just fine but the eclipse plugin isn't picking them up when I execute the eclipse:eclipse goal. It was just a plugin version issue. The newest version picks up the sources just fine. It does not set the javadoc archive, though. Is that functionality supported by the plugin? -dub - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating and using source archive
If you execute 'mvn eclipse:eclipse -DdownloadSources=true', an Eclipse project will be generated with sources or javadocs attached. While you may not want the related project files (.project & .classpath) this will have the side effect of downloading what you need into your local repository. Tom On 4/26/06, gdub <[EMAIL PROTECTED]> wrote: > Good morning- > > We just completed our first Maven-based > project and are on to the next. First, > thanks to the Maven developers for > their efforts and to the members of > this list who were invariably helpful > and patient during the newbie days. > > So, we are moving from the "let's see > how Maven works" phase to the "let's > look at the impact of Maven" phase. > Personally, I have grown from "Maven > child" to "Maven rebellious teenager." > > Now, a thing that would really cut > time would be to have source and javadoc > archives available in the local > repository--for all local and 3rd- > party artifacts. > > So my question is, how can I > automatically install source and javadoc > jars from development projects to the > local repository? I see the instructions > on how to upload them to ibiblio and I > can successfully use the source:jar and > javadoc:jar goals. But how do I get those > jars into my local repository using > Maven?. I know I can copy them directly > but hopefully that's not the recommended > means. Ideally, I'd like it configured so > that building the install goal installs > those jars as well. > > On the comment side, I would like to > plead with ibiblio uploaders to please > include source and javadoc archives > with your packages if at all possible. > I know it's extra work but it could > have a big impact on Maven usability. > > Thanks as always, > >-dub > > > - > 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: creating and using source archive
to get the source into your repository then you need to attache the source plugin to the package phase as below. this will then automatically generate the sources and deploy them. maven-source-plugin 2.0 package jar -Original Message- From: gdub [mailto:[EMAIL PROTECTED] Sent: 26 April 2006 17:01 To: Maven Users List Subject: creating and using source archive Good morning- We just completed our first Maven-based project and are on to the next. First, thanks to the Maven developers for their efforts and to the members of this list who were invariably helpful and patient during the newbie days. So, we are moving from the "let's see how Maven works" phase to the "let's look at the impact of Maven" phase. Personally, I have grown from "Maven child" to "Maven rebellious teenager." Now, a thing that would really cut time would be to have source and javadoc archives available in the local repository--for all local and 3rd- party artifacts. So my question is, how can I automatically install source and javadoc jars from development projects to the local repository? I see the instructions on how to upload them to ibiblio and I can successfully use the source:jar and javadoc:jar goals. But how do I get those jars into my local repository using Maven?. I know I can copy them directly but hopefully that's not the recommended means. Ideally, I'd like it configured so that building the install goal installs those jars as well. On the comment side, I would like to plead with ibiblio uploaders to please include source and javadoc archives with your packages if at all possible. I know it's extra work but it could have a big impact on Maven usability. Thanks as always, -dub - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
