On 7/25/07, Kit Plummer <[EMAIL PROTECTED]> wrote:
As long as I can "comment out" the feature at one place I don't mind the
styleguide stuff. But, you are right...seems like it would be more of a
pre-commit hook thing.
Well the problem is that Subversion commits don't go through the Maven
bui
On 7/25/07, Bruce Snyder <[EMAIL PROTECTED]> wrote:
On 7/25/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> If people find this configuration too painful, we can easily disable
> the checks by default but i thought it was a good way to enforce a
> coherent code format. And yes, all the configur
On 7/25/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
If people find this configuration too painful, we can easily disable
the checks by default but i thought it was a good way to enforce a
coherent code format. And yes, all the configuration will be moved to
a single place when all the componen
Never mind. It has to do with the packaging type handlers and such. I
understand now. Interesting issue.
Dan
On Wednesday 25 July 2007 16:15, Daniel Kulp wrote:
> On Wednesday 25 July 2007 15:52, Guillaume Nodet wrote:
> > Yes it should. The main problem comes from the servicemix maven
>
Yes it should. The main problem comes from the servicemix maven
plugin: it relies ou maven extensions plugins which can not be built
and used in the same run :-( Other ways include fixing maven (if
possible), splitting the release cycles as discussed in an earlier
thread, using an ant file or batc
Guillaume,
What is causing the two step build in the first place? Shouldn't Maven
take care of building everything in the right order automatically, based
on the interdependencies of the subprojects?
Gert
Guillaume Nodet wrote:
I was wondering if someone knows a way to spawn a maven build
I was wondering if someone knows a way to spawn a maven build from
within maven. Maybe this would be a way to remove the two steps build
needed the first time (and when releasing too).
--
Cheers,
Guillaume Nodet
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/
If people find this configuration too painful, we can easily disable
the checks by default but i thought it was a good way to enforce a
coherent code format. And yes, all the configuration will be moved to
a single place when all the components pass the checks.
On 7/25/07, Bruce Snyder <[EMAIL PR
[
https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated SM-939:
Attachment: patch0720.txt
> CXF based Service Engine and Bnding Component
> ---
[
https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated SM-939:
Attachment: (was: patch0720.txt)
> CXF based Service Engine and Bnding Component
>
Armen H.,
We usually don't pick up SNAPSHOT builds in our releases. However, we
are planning to a 3.1.2 release sometime in the near future, so if
ActiveMQ has released the patch by then, we can include it at that time.
Can you already provide me with a reference to a thread on the mailing
11 matches
Mail list logo
