Re: [M2] Are pom.xml settings.xml really well-formed?

2008-02-09 Thread Jason van Zyl

We don't use Xerces, never have, never will.

On 9-Feb-08, at 8:47 AM, Roger Ye wrote:


Hi all,

I've just read haakon's blog Java Permgen space, String.intern, XML
parsinghttp://www.thesorensens.org/?p%3D14
(pitty his permlink is broken), that's a memory problem caused by  
well

formed XMLs,
which is related to the usage of String.intern(), by the XML parser  
Xerces

2.

ccording to (http://xerces.apache.org/xerces2-j/features.html), All  
element

names, prefixes, attribute names, namespace URIs, and local names are
internalized using the java.lang.String#intern(String):String  
method.




The problem is that, the XML is not really well-formed, the tags  
actually

contains data, e.g.


data.6541237895.field1field one val/data.6541237895.field1
data.6541237895.field2field two val/data.6541237895.field2

it was XML for which it would be impossible to write a DTD because  
the *data lived in the tag space*.





And reading the following message recalled the blog, we see

in settings.xml


propertiesdownloadSourcetrue/downloadSource




and in my own pom.xml


   plugin
   groupIdorg.mortbay.jetty/groupId
   artifactIdmaven-jetty-plugin/artifactId
   configuration
   contextPath//contextPath
   scanIntervalSeconds10/scanIntervalSeconds
   /configuration



Here we have the similar problem. both settings.xml and pom.xml are  
not

really well-formed,
better to have:

property name=downloadSourcetrue/property
property name=contextPath//property
..




On 2/9/08, nicolas de loof [EMAIL PROTECTED] wrote:


This works fine for me
(I've set propertiesdownloadSourcetrue/downloadSource in my
settings.xml)

Many artifacts in maven central repo don't have the expected source
bundles.

One option is to build them yourself from source distribution, and  
even
better propose for upload (http://jira.codehaus.org/browse/MAVENUPLOAD 
)


Another option is to contact the developer list and ask them to  
publish
themself the required -sources.jar. This is automatically created  
by maven

during release (if predefine profile is used), so recent
maven2-based-builds
should all have thoses sources.jars.

I'm myself in discution on apache commons dev list to publish  
sources for

archived commons-*

Nico.



2008/2/9, Jan Torben Heuer [EMAIL PROTECTED]:


Hi,

I don't know if I'm doing something wrong, but shouldn't

mvn eclipse:eclipse -DdownloadSources=true

download and reference the sources in eclipse?


Are the sources normally available for libs in the central  
repository? I

mean for example log4j, httpunit, xmlbeans...



Does it work for someone here?

Jan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
--





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [M2] Are pom.xml settings.xml really well-formed?

2008-02-09 Thread Manos Batsis

Roger Ye wrote:


The problem is that, the XML is not really well-formed, the tags actually
contains data, e.g.


data.6541237895.field1field one val/data.6541237895.field1
data.6541237895.field2field two val/data.6541237895.field2



This is well formed XML alright. Element names start with a letter and 
not with any case combo of xml. Whether the design is good or bad is 
another matter.




it was XML for which it would be impossible to write a DTD because the *data 
lived in the tag space*.


Well-formed and valid are terms meaning different things, although a 
valid XML document is of course well-formed.



Cheers,

Manos


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]