why is the linux shell not merged into one but instead are ls and tree and
stuff separate programs?
The answer is: separation of concerns!
Why should we throw this together and thus create a big bunch of unmaintainable
code?
LieGrue,
strub
--- On Thu, 6/30/11, jameslordhz wrote:
> From: jam
after i use mvn eclipse:eclipse, eleven eclipse projects are generated for
maven 3, that is
[maven-aether-provider]
[maven-artifact][maven-compat]
[maven-core][maven-embedder]
[maven-model] [maven-model-builder]
[maven-plugin-api]
Sorry, did not noticed the OOM in the logs! Bot restarted, try again please...
Thanks,
~t~
On Wed, Jun 29, 2011 at 9:34 PM, Wendy Smoak wrote:
> On Wed, Jun 29, 2011 at 2:36 PM, Martin Gainty wrote:
>
>> make ¢?
>
> No. Where did that list come from?
--
On Wed, Jun 29, 2011 at 2:36 PM, Martin Gainty wrote:
> make ¢?
No. Where did that list come from?
I thought maybe the OP was asking about the many modules in the Maven
source code: http://svn.apache.org/repos/asf/maven/maven-3/trunk/
--
Wendy
--
What are you two talking about. In what respect is Maven 3 divided
into this set of eclipse projects?
On Wed, Jun 29, 2011 at 2:36 PM, Martin Gainty wrote:
>
> these are the eclipse (sub)projects i have thus far:
> apache
> cdt
> core
> equinox
> jdt
>
yes i forgot about endorsed... it is definitely required... complicates
plugins that run in the same jvm though... eg jetty, surefire in no fork
mode, etc
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using s
true should get you the non-transitive.
hard to digest the rest of your post with my son pulling out of me ;-)
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 29 Jun 2011 1
these are the eclipse (sub)projects i have thus far:
apache
cdt
core
equinox
jdt
text
wst
if my base eclipse version is 3.7 (for eclipse version 3.7)
and if i implement a new algorithm for EditText or UndoText I would refactor
On 06/27/2011 06:54 PM, Stephen Connolly wrote:
Critically missing from my PoV are:
Consider also 'endorsed' (a serious issue for EE projects especially):
http://jira.codehaus.org/browse/MNG-4752
Also some notes on a non-transitive compile scope: for NetBeans module development, module -> mod
I'm not sure the HTML analogy flies (in particular, I'm not convinced that,
say, schema.org isn't just re-invention of namespaces or RDFa via another
mechanism).
I have no argument that XML namespaces are somewhat klunky, but they are at
least standardised and have well understood transformations
I'm opposed to namespaces for two reasons. One is a global reason, the
other applies only to 'core' configuration.
The global reason: read all the very cogent writing from the HTML5
process as to why they have run screaming away from namespaces.
The more local reason: Consider what started this d
>
>
>
> If tools validate against the schema, they know when a POM is, in
> fact, valid for its declared model. Thus, any elements that the tool
> does not recognize are proved to be 'messengers from the future'.
>
>
It would help enormously if 'messengers from the future' used an appropriate
XML n
I think that you should create a JIRA.
On Wed, Jun 29, 2011 at 7:11 AM, Henika Tekwani wrote:
> Hi All,
>
> I am trying to deploy an artifact using maven 3 but I don't want to update
> the RELEASE tag in the maven-metadata.xml. I am using
> "maven-deploy-plugin:2.6:deploy-file" and while callin
>>
>> Telling people to edit and maintain two poms is also likely to lead to
>> widespread derision.
>>
>> Here's another thought experiment in design. This may merely be me
>> recapitulating Steven's idea. Say that for Maven 3.1 we wanted to fix
>> this issue once and for all. So, we make maven 3.
On 29 June 2011 12:20, Benson Margulies wrote:
> If they update to new versions of the thing with the pom. At least for
> polemic purposes, imagining a world in which the decision to make use
> of a new pom feature has the effect of forcing these sticks-in-the-mud
> to stick to old versions.
>
> L
If they update to new versions of the thing with the pom. At least for
polemic purposes, imagining a world in which the decision to make use
of a new pom feature has the effect of forcing these sticks-in-the-mud
to stick to old versions.
Let me be more specific about why I don't like the alternati
Hi All,
I am trying to deploy an artifact using maven 3 but I don't want to update the
RELEASE tag in the maven-metadata.xml. I am using
"maven-deploy-plugin:2.6:deploy-file" and while calling the deploy command I am
setting -DupdateReleaseInfo=false. Still the RELEASE tag in metadata is gettin
17 matches
Mail list logo
