On Monday, December 12, 2011 9:43:37 AM a...@apache.org wrote:
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:wsrmp=http://schemas.xmlsoap.org/ws/2005/02/rm/policy;
- xmlns:beans=http://www.springframework.org/schema/beans;
+
I think that there might be an advantage in declaring the maven
plugins to be an independent top-level that we release after a release
of the core product, (and perhaps release in-between as needed).
There's a pattern to maven plugin projects at maven.apache.org or the
Mojo project at codehaus,
Hi Dan,
okay. you are right. I just removed the bp reference but forgot the
same problem can happen in the other end as well. i will remove the
spring schema reference too.
thanks.
regards, aki
2011/12/12 Daniel Kulp dk...@apache.org:
On Monday, December 12, 2011 9:43:37 AM a...@apache.org
Aki,
I've attached a diff that might be usable. Can you give it a try?
Dan
On Monday, December 12, 2011 2:49:51 PM Aki Yoshida wrote:
Hi Dan,
okay. you are right. I just removed the bp reference but forgot the
same problem can happen in the other end as well. i will remove the
spring
Oh, glorp. I'd like to get the wsdl2js mojo in place, but I don't know
if I can do it fast enough. I'll try to finish it tonight.
On Mon, Dec 12, 2011 at 9:20 AM, Daniel Kulp dk...@apache.org wrote:
There were a bunch of changes over the weekend and a couple of regressions so
I want to delay
On Monday, December 12, 2011 8:11:43 AM Benson Margulies wrote:
I think that there might be an advantage in declaring the maven
plugins to be an independent top-level that we release after a release
of the core product, (and perhaps release in-between as needed).
There's a pattern to maven
I'll answer your question with a question.
Could the maven plugins be in the build last, so that they could have
the same sort of integration tests as all the maven plugins at Maven
and Mojo? If so, I completely withdraw my idea. If not, I guess I
can't make a really good argument, and the tests
On Monday, December 12, 2011 11:41:34 AM Benson Margulies wrote:
I'll answer your question with a question.
Could the maven plugins be in the build last, so that they could have
the same sort of integration tests as all the maven plugins at Maven
and Mojo?
Well, no. We need the plugins
On Tue Dec 13 00:56:21 2011, Daniel Kulp wrote:
On Monday, December 12, 2011 11:41:34 AM Benson Margulies wrote:
I'll answer your question with a question.
Could the maven plugins be in the build last, so that they could have
the same sort of integration tests as all the maven plugins at Maven
We haven't got much in the way of tests here. I found a few zingers
while refactoring (e.g. a ConcurrentModification problem from deleting
from an ArrayList in mid-iteration). But I don't feel all that certain
that I have not added some bugs as well.
It would be good if people could cook more
When I try to add the js tooling to the codgen plugin as a dependency
to enable the js mojo, I get whacked with this.
Any suggestions?
[ERROR] The projects in the reactor contain a cyclic reference: Edge
between 'Vertex{label='org.apache.cxf:cxf-codegen-plugin:2.5.1-SNAPSHOT'}'
and
This charming message is a fraud. the loop related to plugin
executions and is the reason why I shouldn't have put any codegen
executions in the javascript runtime pom.
On Mon, Dec 12, 2011 at 9:40 PM, Benson Margulies bimargul...@gmail.com wrote:
When I try to add the js tooling to the codgen
On Monday, December 12, 2011 9:52:24 PM Benson Margulies wrote:
This charming message is a fraud. the loop related to plugin
executions and is the reason why I shouldn't have put any codegen
executions in the javascript runtime pom.
Well, it's actually more than just the codegen plugin in
13 matches
Mail list logo
