I am finalizing my jaxb2 plugin which I would hope to publish.
However, there is something crazy, if I look at the m2e-extras
as an example on how to test my connector. This is pretty ugly,
there is a remoterepo which is basically a copy of the artifacts
the project needs and a settings.xml which
I am finalizing my jaxb2 and xmlbeans connectors in the next few days.
Just letting you guys know.
They are available: https://github.com/bitstrings/m2e-connectors
Pino Silvaggio
___
m2e-users mailing list
m2e-users@eclipse.org
https
Ok, so I pretty much have something solid.
Both jaxb2 and xmlbeans connectors seem to work.
But, there something I am not sure...
When the build is triggered, i.e.: modified file(s) in schema directory
the generated-sources is no cleaned... therefore there could be sources
that shouldn't be t
When trying to use source:jar-no-fork (or even source:jar)
I get:
[WARNING] NOT adding sources to artifacts with classifier as Maven only
supports one classifier per artifact. Current artifact
[org.bitstrings.eclipse.m2e.connectors.jaxb2:org.bitstrings.eclipse.m2e.connectors.jaxb2:eclipse-plug
What is the desired behaviour for a connector supporting code generation?
For example, if I "clean" a project shouldn't the connector rebuild
everything?
Because as it stands right now the project becomes stale
and we have to explicitly recompile (build) to make it refresh.
Not so clean in my
clean(IProgressMonitor) should delete all generated
sources, but in many cases this is not easy to implement because of
discrepancy between how maven and eclipse approach.
--
Regards,
Igor
On 11-07-25 4:51 AM, Pino Silvaggio wrote:
What is the desired behaviour for a connecto
Here's an example, i got a jaxb2 connector which verifies change
in xsd(s) and build/refresh if necessary. However, what if I change
the catalog parameter or the packageName in the configuration
of the plugin?
My question, do we have to check every possible parameters
and if so, how do we do that
Maybe there's something I don't see but why isn't there support
for unpack and copy?
Wouldn't the connector just refresh the "outputDirectory"?
There's no need for really checking or building anything...
or am I wrong?
___
m2e-users mailing list
m2e-
How and what logger should I use in my connector?
Where does the output go?
___
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
Connector for the org.apache.maven.plugins:dependency plugin unsupported
goals.
P2 Repository: http://bitstrings.github.com/m2e-connectors-p2/milestones
Supported goals:
unpack
unpack-dependencies
copy
copy-dependencies
Sources: https://github.com/bitstrings
_
I am working hard to resolve all the issues our developers encounter.
Main problem is that none of our ~70 projects import without a bunch of
error markers. I don't understand how this is good. It's simply
unacceptable. It's warning kinda of an error but not really... Sure it's
fun to know th
Hi,
just noticed that my connectors (m2e-xmlbeans-connector and
m2e-jaxb-connector) are not
in the catalog of m2e 1.1.0. In fact, other connectors aren't there
either...
Is this because I need to update my connectors to work with 1.1.0 (API
change...)?
_
elper [0.15.0.201109282249]
On 10/03/2011 03:18 PM, Matthew Piggott wrote:
I believe if you already have them install they are hidden in the dialog.
On 3 October 2011 15:16, Pino Silvaggio <mailto:pino.silvag...@gmail.com>> wrote:
Hi,
just noticed that my connectors (m2e-xmlbeans-connect
Yep, range is tight.
I will release a new version very soon.
On 10/03/2011 03:29 PM, Matthew Piggott wrote:
Which version of m2e do you have installed? It appears to be 1.1
(unreleased), if so it looks like your version range is too tight.
On 3 October 2011 15:25, Pino Silvaggio
Hi,
I am currently testing my connectors with m2e 1.1 found on sonatype
forge site.
There seem to be a problem with the build where *build(int kind,
IProgressMonitor monitor)*
doesn't really build and my tests fail with the project having an error
marker.
This is the same code working on m
ll have a look.
>
>And just to confirm, project configurators that worked with m2e 1.0 and
>did not use any .internal. m2e classes are expected to work with 1.1.
>
>--
>Regards,
>Igor
>
>
>On 11-10-20 6:22 PM, Pino Silvaggio wrote:
>> Hi,
>>
>> I am
--
>Regards,
>Igor
>
>On 11-10-20 8:14 PM, Pino Silvaggio wrote:
>> i will investigate further but fyi m2e extras antlr tests fail,
>granted with a different error but still...
>>
>> Igor Fedorenko wrote:
>>
>>> This sounds like a bug, but I do not un
tlr tests from m2e-extras repo? I just checked out
>0.13.0.20110622-1538 tag, fixed version ranges in bundle manifests and
>was able to successfully run antlr tests from my m2e 1.1 development
>workspace.
>
>--
>Regards,
>Igor
>
>On 11-10-20 8:14 PM, Pino Silvaggio wrote:
those
that do not exist in workspace.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=361549
--
Regards,
Igor
On 11-10-20 8:56 PM, Pino Silvaggio wrote:
forgot to mention that i test with indigo.
Let me create a small test that i can send you.
the error for antlr is simply the assert testin
entries for all
>compile and test compile roots found in MavenProject, even for those
>that do not exist in workspace.
>
>[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=361549
>
>--
>Regards,
>Igor
>
>On 11-10-20 8:56 PM, Pino Silvaggio wrote:
>> forgot to mentio
Hey, if you are using the m2e 1.1.0 snapshot and you require
jaxb2/xmlbeans support, you may want to try version 2.0.0 the connectors
here:
http://bitstrings.github.com/m2e-connectors-p2/milestones
These also work for m2e 1.0.0.
___
m2e-users mailin
For interested people,
New Home: bitstrings.org
milestones (supports m2e 1.1.0):
http://bitstrings.github.com/m2e-connectors-p2/milestones
Plugin mapping
Plugin: org.jvnet.jaxb2.maven2:maven-jaxb2-plugin (maven-jaxb20-plugin,
maven-jaxb21-plugin, maven-jaxb22-plugin)
Home: http://ja
http://bitstrings.github.com/
(available from main catalog)
___
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
What if the plugin is a profile, what is the expected behaviour?
I mean how should m2e react to profiles that contain mapped plugins?
In fact how can you select profiles in m2e?
___
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/m
Hello,
so we have a project which filters xsds and the result is of course
under target/xsd.
When importing this project the generated-sources are not available (not
generated).
The filtered xsds are there but the maven-jaxb2-plugin doesn't see it
(it uses the buildContext scanner which re
25 matches
Mail list logo
