Hi.
>> Where could I find it?
>
> You can find my 'jaxb1-maven-plugin' here:
> http://jira.codehaus.org/browse/MOJO-374
Ok, I've checked it out...
The problem I see is that the plugin you've posted is quite different from jaxb2
plugin from jaxb2-sources (default configuration, directory layout, etc). I
think it's important to make maven plugins consistent between jaxb 2 versions.
Since jaxb2 plugin is already there I suggest using their layout (they have
schema *.xsd and bindings *.xjb in src/main/resources,
target/generated-sources/xjc as target dir) etc.
Further problem is that your plug-in does not support the configuration of xjc
arguments which are necessary for XJC add-ons.
There's a couple more problems I see with your plugin, but of course nothing
tragic.
In the meanwhile I've quickly ported the jaxb2 maven plugin onto jaxb1. This is
already committed into the CVS, so I'd suggesting taking this as a basis and
merge with your plugin.
> For not having to go through the JIRA issue i mentioned above
> (although you should do it for learning my history :-)), here are the
> dependencies of my jaxb1 plugin:
Ok, I don't have sax, dom, xerces and xalan dependencies at the moment...
> The first thing to do is to decide a proper name. I had decided to
> use exactly like the one you used (jaxb1-maven2-plugin) but
> mojo.housemates persuade me to drop the '2' from the 'maven2' part.
> Anyway, considering the existent confusion regarding maven1/2, and
> that it is a different project, i believe that the
> 'jaxb1-maven2-plugin' is the right name to use.
Quite agree.
> I will update my JIRA issue pointing to your plugin. Also, notice that
> my code had undergone some changes, by Anders Kr. Andersen who wished
> to generate sources outside the 'target' dir, and eventually ended up
> re-inventing the...clean-plugin. Although he has a point, i'm not so
> much of including this functionality in the plugin... (i'm sorry
> Anders, can't you use the ant-run plugin instead ?).
I don't think this functionality belongs to the plugin, so I'd suggest dropping
it out.
>> I hope you have seen:
>> https://maven-repository.dev.java.net/
>> And:
>> https://maven-repository.dev.java.net/repository/
>
> Of course. I posted my emails under their mailing-list
> 'users_at_maven-repository.dev.java.net' too.
> I have also posted them in the 'dev_at_hyperjaxb2.dev.java.net'.
>
> I think you should make an announcement about the new
> jaxb1-maven2-plugin project
> under at least those lists.
I'd test the plugin a bit first. dev_at_hyperjaxb2 is inhabited, better refer to
users_at_hyperjaxb.dev.java.net.
And I'm afraid I can fail on time with documentation and promotion of the
plugin. Could you help on this point?
>> 1. Create a new jaxb1-maven2-plugin project on dev.java.net.
>> 2. Use dev.java.net repository and dependencies I posted above.
>> 3. Wait for Kohsuke to post the xsdlib, manually add the jar to the
>> local repo
>> for the moment.
>>
>> I've just created jaxb1-maven2-plugin project. Please apply for the
>> developer
>> role and post your code there:
>> https://jaxb1-maven2-plugin.dev.java.net/
>
> What about the hyperjaxb2 plugin ???
hyperjaxb2 depends on jaxbcommons and it also needs a jaxb1 maven2 plugin. I
hope I'll move hyperjaxb2 onto maven quite soon.
There's actually no need in a special plugin for hyperjaxb2, it can be simply
added into jaxb1 plugin dependencies.
>> Later on we'll be able to use dev.java.net maven automatismus to post
>> the plugin
>> into the repo automatically.
>
>
> If i'm not mistaken, this automatism is for maven1, right ?
>
> We probably need to make a new one for maven2, see this:
>
> https://maven-repository.dev.java.net/servlets/ReadMsg?list=users&msgNo=2
Right.
Bye.
/lexi