I believe this warning happened when the Axis dependency was moved to 
1.3.  We don't use attachments but it is on the Jira tracker for future 
incorporation using some SOAP library (TBD).  If this passes regression 
testing it would be nice to have a clean Axis 1.3 with no warnings even 
though we are not using attachments.  It was on my list but would like 
some collective intelligence on Axis.

On vaguely related subject, in the client (now fedora-admin-client) 
stubwrappers is a separate source directory.  That and the generated 
sources are not being handled well in the Eclipse configuration.  This 
does not affect the Maven build, only the use of the tooling and refreshing.

I have one warning in the "How do you configure Eclipses for Fedora with 
Maven?" article about directories with spaces but I will extend it to 
cover the case (everyone is invited to add or comment with Eclipse/Maven 
knowledge directly in the article).  The first version of the article is 
largely complete (thanks to Eddie for his timely contributions).  
However, it bears checking for accuracy and there is great room for 
improvement.

I will add a set up instruction for UTF-8 in the article.  Also, I can 
set the encoding on the POMs if we have a consensus.

-- Dan

Chris Wilper wrote:
> I agree with setting UTF-8 in the pom as Kai suggests.  I was getting
> a similar warning and had the same concern about non-reproducible
> builds.
>
> If the coding guidelines don't already mention it, I think we need to
> standardize on UTF-8 for any text files in the source tree.  Thus,
> Eclipse (or any IDE) should be forced to use UTF-8 as well, if
> possible.
>
> I think line ending characters "don't matter" as long as we've all got
> our svn autoprops set correctly.
>
> Kai said:
>   
>>> Regarding the "Attachement support is disabled" warning I've found
>>> that adding javax.activation and javax.mail to the dependencies of the
>>> axistool-maven-plugin in common/pom.xml will make it disappear.
>>>       
>
> Maybe we should check this change in too?  Any downside?
>
> - Chris
>
> On Fri, Oct 30, 2009 at 8:10 AM, Daniel Davis <[email protected]> 
> wrote:
>   
>> Should we set a uniform encoding in Eclipse  (and other editors)?  Also
>> line termination?
>>
>> -- Dan
>>
>> Steve Bayliss wrote:
>>     
>>> Hi Kai
>>>
>>> Thanks for that - yes it does sound like a good idea to specify the encoding
>>> in the pom.xml.
>>>
>>> Regards
>>> Steve
>>>
>>> -----Original Message-----
>>> From: Kai Strnad [mailto:[email protected]]
>>> Sent: 30 October 2009 10:48
>>> To: Steve Bayliss
>>> Cc: 'Chris Wilper'; [email protected]
>>> Subject: Re: [Fedora-commons-developers] Problems building trunk
>>>
>>>
>>> Hi Steve,
>>>
>>> the encoding can be changed by adding the following property to
>>> <properties> section of the pom.xml:
>>>
>>> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
>>>
>>> Perhaps we should generally set this property in order to avoid
>>> potentially irreproducable builds due to the usage of default platform
>>> encodings (MacRoman, Cp1252, etc).
>>>
>>> Regarding the "Attachement support is disabled" warning I've found
>>> that adding javax.activation and javax.mail to the dependencies of the
>>> axistool-maven-plugin in common/pom.xml will make it disappear.
>>>
>>> Regards,
>>> Kai
>>>
>>>
>>>
>>>
>>>       
>>>> Hi Chris, Andrew
>>>>
>>>> Think I may have got to the bottom of this.  I tried esing an Eclipse
>>>> workspace "C:\workspace", and it seems to build fine.  Then tried
>>>> another -
>>>> "C:\work space" - and it failed.  So it looks like there's a problem
>>>> building if there are spaces in the path.  I've added FCREPO-566 for
>>>> this.
>>>>
>>>> Secondary issue/comment - I'm getting warnings "[WARNING] File
>>>> encoding has
>>>> not been set, using platform encoding Cp1252, i.e. build is platform
>>>> dependent!" - is there some way of setting the encoding so it
>>>> doesn't use
>>>> the platform encoding?
>>>>
>>>> Regards
>>>> Steve
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: [email protected] [mailto:[email protected]] On Behalf Of
>>>> Chris Wilper
>>>> Sent: 30 October 2009 01:56
>>>> To: Steve Bayliss
>>>> Cc: Andrew Woods; [email protected]
>>>> Subject: Re: [Fedora-commons-developers] Problems building trunk
>>>>
>>>>
>>>> Hi Steve,
>>>>
>>>> As Andrew pointed out, the readme.txt was out of date; it's now
>>>> fixed in
>>>> svn.
>>>>
>>>> I've seen the "Attachement support is disabled" warning before, but it
>>>> wasn't causing the build to fail.  See
>>>>
>>>>
>>>>         
>>> https://fedora-commons.org/bamboo/build/viewBuildLog.action?buildNumber=194&;
>>>
>>>       
>>>> buildKey=FCREPO-LINUXSAN
>>>> for an example...the warning looks like the one you're getting, but
>>>> the tests still run successfully.
>>>>
>>>> I tried doing a clean build locally, and did not get the error you're
>>>> seeing.  I got a different series of errors (!); all the ResourceIndex
>>>> integration tests failed, apparently due to a failure to initialize
>>>> the test triplestore.
>>>>
>>>> Then when I made the readme.txt checkin, this triggered another
>>>> automatic build on the test server, which failed differently.
>>>>
>>>> So now there are 3 separate build errors to track down.
>>>>
>>>> 1) The one you're reporting in your environment (Windows).  I will try
>>>> a build in Windows and see if I get similar behavior.
>>>> 2) The ones I'm seeing in my dev environment (OS X).  I plan to look
>>>> at this in more detail, but for now have attached the log for one of
>>>> those in case it rings any bells with anyone.
>>>> 3) The one that occurred on the integration test server (Linux).  The
>>>> client-side stack trace is here:
>>>>
>>>>
>>>>         
>>> https://fedora-commons.org/bamboo/browse/FCREPO-LINUXSAN-195/artifact/All-Su
>>>
>>>       
>>>> refire-Reports/integrationtest/target/surefire-reports/
>>>> fedora.test.integrati
>>>> on.cma.ContentModelDSInputTest.txt
>>>> ...and the server-side stacktrace is here (grep for
>>>> HttpServiceNotFoundException):
>>>>
>>>>
>>>>         
>>> https://fedora-commons.org/bamboo/browse/FCREPO-LINUXSAN-195/artifact/Server
>>>
>>>       
>>>> -and-Catalina-Logs/fedora.test.AllSystemTestsConfigB/fedora.log
>>>> No great insights on this one yet, but I confirmed that it is
>>>> intermittent -- I manually triggered another ci build and it
>>>> succeeded:
>>>>
>>>>
>>>>         
>>> https://fedora-commons.org/bamboo/build/viewBuildLog.action?buildNumber=196&;
>>>
>>>       
>>>> buildKey=FCREPO-LINUXSAN
>>>>
>>>> - Chris
>>>>
>>>> On Thu, Oct 29, 2009 at 9:08 PM, Steve Bayliss
>>>> <[email protected]> wrote:
>>>>
>>>>         
>>>>> Hi Andrew
>>>>>
>>>>> I've given that a try, I'm still getting an error:
>>>>>
>>>>> 30-Oct-2009 01:03:04 org.apache.axis.utils.JavaUtils
>>>>> isAttachmentSupported
>>>>> WARNING: Unable to find required classes
>>>>> (javax.activation.DataHandler and
>>>>> javax
>>>>> .mail.internet.MimeMultipart). Attachment support is disabled.
>>>>>
>>>>> ...
>>>>>
>>>>> Caused by: java.io.FileNotFoundException: C:\Documents and
>>>>>
>>>>>
>>>>>           
>>>> Settings\stephen.bayliss\workspace\fedora-repository\resources
>>>> \fedora-types.
>>>>
>>>>         
>>>>> xsd (The system cannot find the file specified)
>>>>> ...
>>>>>
>>>>> I'm attaching the full output in case that helps!
>>>>>
>>>>> Steve
>>>>>
>>>>> -----Original Message-----
>>>>> From: Andrew Woods [mailto:[email protected]]
>>>>> Sent: 30 October 2009 00:44
>>>>> To: Steve Bayliss
>>>>> Cc: [email protected]
>>>>> Subject: Re: [Fedora-commons-developers] Problems building trunk
>>>>>
>>>>>
>>>>> Hello Steve,
>>>>> The readme.txt was out of date. The "installLibs.sh" script was
>>>>> required before Duraspace began hosting Maven2 artifacts that are
>>>>> required by Fedora but not available elsewhere in its own publicly
>>>>> accessible Maven2 repository. Could you try using the following build
>>>>> command?
>>>>>
>>>>>   maven clean install
>>>>>
>>>>> Andrew
>>>>>
>>>>> On Thu, Oct 29, 2009 at 5:10 PM, Steve Bayliss
>>>>> <[email protected]> wrote:
>>>>>
>>>>>           
>>>>>> I've basically followed the instructions here:
>>>>>>
>>>>>>
>>>>>>
>>>>>>             
>>> http://www.fedora-commons.org/confluence/pages/viewpage.action?pageId=137656
>>>
>>>       
>>>>> 55 ("How
>>>>>
>>>>>           
>>>>>> do you configure Eclipse for Fedora with Maven?")
>>>>>>
>>>>>> I've grabbed everything out of Subversion (trunk), and I'm trying to
>>>>>>
>>>>>>             
>>>>> build.
>>>>>
>>>>>           
>>>>>> Readme.txt has:
>>>>>> -----
>>>>>>    1. Until dependencies are found in a public repository,
>>>>>>       the following script needs to be run
>>>>>>           * ./resources/scripts/installLibs.sh
>>>>>>    2. mvn install -P fedora-installer
>>>>>>           * generates fedora-installer.jar
>>>>>>           * found in /installer/target
>>>>>> -----
>>>>>> However I don't see an installLibs.sh script - only
>>>>>> uninstallLibs.sh (and
>>>>>> .bat).
>>>>>>
>>>>>> And when I try and build using step 2, I get the errors below.
>>>>>>
>>>>>> What am I doing wrong?
>>>>>>
>>>>>> [INFO] Processing wsdl: C:\Documents and
>>>>>> Settings\stephen.bayliss\workspace\fedo
>>>>>> ra-repository\common\..\resources\wsdl\Fedora-API-M.wsdl
>>>>>> 29-Oct-2009 20:51:53 org.apache.axis.utils.JavaUtils
>>>>>>
>>>>>>             
>>>> isAttachmentSupported
>>>>
>>>>         
>>>>>> WARNING: Unable to find required classes
>>>>>> (javax.activation.DataHandler
>>>>>>
>>>>>>             
>>>> and
>>>>
>>>>         
>>>>>> javax
>>>>>> .mail.internet.MimeMultipart). Attachment support is disabled.
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [ERROR] BUILD ERROR
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] Error generating Java code from WSDL.
>>>>>>
>>>>>> Embedded error: Error running Axis
>>>>>>
>>>>>>
>>>>>>             
>>> ----------------------------------------------------------------------------
>>>
>>>       
>>>>> --
>>>>>
>>>>>           
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>>>> is the only developer event you need to attend this year.
>>>>>> Jumpstart your
>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>> and stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Fedora-commons-developers mailing list
>>>>>> [email protected]
>>>>>> https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
>>>>>>
>>>>>>
>>>>>>
>>>>>>             
>>> ----------------------------------------------------------------------------
>>>
>>>       
>>>> --
>>>>
>>>>         
>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>>> is the only developer event you need to attend this year. Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market
>>>>> and stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Fedora-commons-developers mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/fedora-commons-
>>>>> developers
>>>>>
>>>>>
>>>>>
>>>>>           
>>>>         
>>> ----------------------------------------------------------------------------
>>> --
>>>
>>>       
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market and
>>>> stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Fedora-commons-developers mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
>>>>
>>>>         
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Fedora-commons-developers mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
>>>
>>>       
>> --
>> Daniel W. Davis
>> Cornell University
>> Fedora Commons Affiliate
>> http://fedora-commons.org
>> [email protected]
>> (607) 255-6090 (Office)
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Fedora-commons-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
>>
>>     

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers

Reply via email to