Kostis Anagnostopoulos wrote:
> Actually Aleksei already created the jaxb1-maven2-plugin.dev.java.net project.
> I think its up to you, Koshuke, to decide where the plugin should be.
> I 'm not certain as to whether maven plugins should be co-hosted with
> the parent project or in a separate one. Nevertheless, i firmly
> believe that the main project documents must explicitly refer to the
> maven plugins.
I'm fine either way. Looks like that project is already seeded with the
source code, so why don't we just keep it like this, then.
It would be good if
https://jaxb1-maven2-plugin.dev.java.net/ page is
updated to explain what the project is, etc.
Once it's ready, I agree that the main website should refer to it.
>> I worked on the maven1 plugin for java.net in
>> http://maven-javanet-plugin.dev.java.net/, and I'm trying to do a
>> similar thing for maven2. If you are interested in helping that effort
>> too, that would be greatly appreciated.
>
> Yes I'm interested in helping towards unifying maven2 building process
> with dev.java.net. I begin right now :-), by stating that it may not
> necessary to build another plugin! It would rather be easier to work
> with pre-existent ones (i.e. release-plugin).
>
> Waiting from you for any guidance regarding the above matter (what
> mailing-lists to use, who to contact, design and architecture).
I think users_at_maven-repository.dev.java.net is the good place to discuss
this.
I've been tinkering with m2 a bit, and I agree with you that there are a
lot that existing plugins can do. In particular, the wagon-scm module in
the sandbox turns out to be really useful for:
1) pushing the generated site to java.net webspace
(which is in CVS or SVN)
2) pushing bits to the maven repository
The part that I think is missing right now is how to upload files to the
documents&files section of a java.net project.
We can talk more in the users_at_maven-repository.dev.java.net.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com