You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2013/09/06 23:29:03 UTC
Build and prep for 2.11.0
Is everything ready?
All the modules are now integrated into the build and the snapshots will
now be what the release is except for signing and version numbers so
please poke and prod the builds.
I've made some changes:
1/ Instead of the default being a developer build, the default is a
complete build and there is a restricted set of modules built with
profile "dev". This is to avoid mistakes doing a release :-)
The Jenkins deploy job is now doing a full build (which takes 15mins on
my machine even without any uploads).
The Jenkins test job is a -Pdev build.
Maybe we need more profiles. Please take a look and see what
improvements can be made.
2/ jena-spatial now in the Fuseki server build
Still need to check the distribution versions of NOTICE and LICENSE but
jena-spatial only adds com.spatial4j:spatial4j over what that added by
jena-text.
3/ Include SDB in apache-jena
jena-sdb in the apache-jena lib/ directory.
Not sure is this is the right thing to do - opinions? options?
4/ The website needs link checking
Could someone volunteer and run a link checker on the staging site? I
think some of converted pages may have bad internal links - this is
probably not new.
5/ The build exceptions in JDBC / JenaStatement
... are really quite worrying to the RM!
6/ An "advanced notice" email sent to users@
Andy
Re: Build and prep for 2.11.0
Posted by Andy Seaborne <an...@apache.org>.
The full build on Jenkins has started to hang again in
org.apache.jena.jdbc.remote.results.TestRemoteEndpointResultsWithAuth
Wild guess: because Fuseki is running first and is holding on to some
sockets. Or just bad luck, running on a server that is doing other
stuff. The full build works for me locally.
Just for now, I've made an emergency change of skipping jena-jdbc in the
hope of getting the Fuseki+spatial build done.
Andy
On 06/09/13 22:29, Andy Seaborne wrote:
> Is everything ready?
>
> All the modules are now integrated into the build and the snapshots will
> now be what the release is except for signing and version numbers so
> please poke and prod the builds.
>
> I've made some changes:
>
> 1/ Instead of the default being a developer build, the default is a
> complete build and there is a restricted set of modules built with
> profile "dev". This is to avoid mistakes doing a release :-)
>
> The Jenkins deploy job is now doing a full build (which takes 15mins on
> my machine even without any uploads).
>
> The Jenkins test job is a -Pdev build.
>
> Maybe we need more profiles. Please take a look and see what
> improvements can be made.
>
> 2/ jena-spatial now in the Fuseki server build
>
> Still need to check the distribution versions of NOTICE and LICENSE but
> jena-spatial only adds com.spatial4j:spatial4j over what that added by
> jena-text.
>
> 3/ Include SDB in apache-jena
>
> jena-sdb in the apache-jena lib/ directory.
>
> Not sure is this is the right thing to do - opinions? options?
>
> 4/ The website needs link checking
>
> Could someone volunteer and run a link checker on the staging site? I
> think some of converted pages may have bad internal links - this is
> probably not new.
>
> 5/ The build exceptions in JDBC / JenaStatement
>
> ... are really quite worrying to the RM!
>
> 6/ An "advanced notice" email sent to users@
>
> Andy
Re: Build and prep for 2.11.0
Posted by Andy Seaborne <an...@apache.org>.
On 08/09/13 08:03, Claude Warren wrote:
> Are the javadocs for the new projects (jdbc and security) supposed to be
> available now on staging? If so they are missing. If not "never mind"
>
> Claude
Updating the javadoc is part of the release but you're welcome to put a
copy from the snapshot build there for now.
https://cwiki.apache.org/confluence/display/JENA/Release+Process
Andy
Re: Build and prep for 2.11.0
Posted by Claude Warren <cl...@xenei.com>.
Are the javadocs for the new projects (jdbc and security) supposed to be
available now on staging? If so they are missing. If not "never mind"
Claude
On Sat, Sep 7, 2013 at 9:55 PM, Rob Vesse <rv...@yarcdata.com> wrote:
> Comments inline:
>
>
> On 9/7/13 12:50 PM, "Andy Seaborne" <an...@apache.org> wrote:
>
> >Hi Rob,
> >
> >I've got the full build (deploy) building by using java7. It's not that
> >it is always broken with Java6. The test build is still Java 6 and that
> >usually works; it might be load-on-build-server sensitive. It builds
> >fully on my local machine in either set up. (I have added connection
> >caching to Fuseki test as well.)
> >
> > > What are the build exceptions in JDBC / JenaStatement?
> >
> >There's log at:
> >
> >https://builds.apache.org/job/Jena_Development_Deploy/437/console
> >
> >from about 25% to 50% of the scroll bar.
> >
> >I have a version locally that is clean. I found that the tests reset
> >Log4j and then remove all the appenders which causes the warning about
> >
> >log4j:WARN No appenders could be found for logger
> >(org.apache.jena.riot.stream.JenaIOEnvironment).
> >etc
> >
> >but it also stops configuring the logging from src/test/resources as
> >this is ignored. That confused me for a while :-)
> >
> >I'd guess this was just debugging setup? Also, there is logging to a
> >file, I switched that off as well.
>
> This was kind of intentional, when I was debugging in isolation prior to
> having Jena as a parent I guess the src/test/resources was never applicable
>
> >
> >jena-jdbc-log4j.properties, which is src/main so goes in the final jar
> >but as far as I can see, it's only used in TestMemDriverWithLogging.
>
> This was primarily intended as an example for users, it does also get used
> to test that the JDBC connection parameter for logging works correctly in
> that test class as noted.
>
> >
> >A question:
> >
> >The POM says aspectj plugin is for debugging purposes.
> >
> >(and how do you get it working with Eclipse? When I add a maven nature
> >I get errors and Eclipse refuses to compile the JDBC projects).
>
> There is an AspectJ Development Tools (AJDT) that you can install which
> provides AspectJ support within Eclipse. AspectJ is used to add method
> entry and exit trace logging which is very useful when trying the drivers
> with a new tool to see where (if anywhere) things break.
>
> Rob
>
> >
> > Andy
> >
> >
>
>
--
I like: Like Like - The likeliest place on the web<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Build and prep for 2.11.0
Posted by Andy Seaborne <an...@apache.org>.
On 14/09/13 01:50, Rob Vesse wrote:
> No, the jena-jdbc-driver-bundle module is set up to build a consolidated
> set of javadocs for all the JDBC modules
>
> Rob
>
>
> On 9/13/13 5:24 AM, "Andy Seaborne" <an...@apache.org> wrote:
>
>> Rob -
>>
>> is the right JDBC javadoc for the website that from jena-jdbc-core?
>>
>> Andy
>
OK - I'll use that,
Andy
Re: Build and prep for 2.11.0
Posted by Rob Vesse <rv...@yarcdata.com>.
No, the jena-jdbc-driver-bundle module is set up to build a consolidated
set of javadocs for all the JDBC modules
Rob
On 9/13/13 5:24 AM, "Andy Seaborne" <an...@apache.org> wrote:
>Rob -
>
>is the right JDBC javadoc for the website that from jena-jdbc-core?
>
> Andy
Re: Build and prep for 2.11.0
Posted by Andy Seaborne <an...@apache.org>.
Rob -
is the right JDBC javadoc for the website that from jena-jdbc-core?
Andy
Re: Build and prep for 2.11.0
Posted by Andy Seaborne <an...@apache.org>.
I hope to do the build tomorrow (2013-09-12).
Andy
Re: Build and prep for 2.11.0
Posted by Andy Seaborne <an...@apache.org>.
I have (I hope!) fixed the logging in tests.
The Fuseki test support code was manipulating the logging directly so
that whether logging messages appeared could depend if the test class
ran before or after firing up a background Fuseki test server. Also,
there was a stray log4j.properties in the Fuseki main jar.
The jena-jdbc tests now use log4j.properties from test/resources for
setting logging.
A this point, things should be stable and I hope to call the VOTE later
this week.
If you want to start doing checking early, then you could do so now and
then just verify there have been no relevant changes.
Andy
Jenkins is having an off moment - I've done a build/deploy directly
timestamp around 20130909.203300 and later which for Fuseki is build #21.
Re: Build and prep for 2.11.0
Posted by Andy Seaborne <an...@apache.org>.
On 08/09/13 17:56, Rob Vesse wrote:
> They remove all appenders because things other than JDBC may have caused
> the loggers to be set up some way and doing
> BasicConfigurer.configure()/BasicConfigurer.resetConfiguration() ends up
> setting up a single console appender.
In the tests, the log4j setup should be isolated to each surefire run
and pick up log4j.properties from src/test/resources
(but that's just my assumption/understanding; reality may differ).
> If you have a better way of disabling logging for the tests then that
> would be preferred. Also the one TestMemDriverWithLogging class
> explicitly wants to configure logging because it is changing the logging
> setup at driver creation time to verify that portion of functionality.
> Currently this is redirecting stdout to a ByteArrayOutputStream so as to
> not pollute the build output.
>
> I likely need to add a note to the documentation about example logging
> configuration being available.
>
>
> I'm away on vacation through Wednesday so don't expect any responses from
> me in the meantime I.e. don't let me hold you up if you want/need to make
> changes to get the release prepared.
Ok - I'll checking my logging setup for testing. I'm not touching the
fucntionality of src/main.
Enjoy the vacation time.
Andy
>
> Rob
>
> On 9/8/13 2:20 AM, "Andy Seaborne" <an...@apache.org> wrote:
>
>> On 07/09/13 21:55, Rob Vesse wrote:
>>> Comments inline:
>>>
>>>
>>> On 9/7/13 12:50 PM, "Andy Seaborne" <an...@apache.org> wrote:
>>>
>>>> Hi Rob,
>>>>
>>>> I've got the full build (deploy) building by using java7. It's not
>>>> that
>>>> it is always broken with Java6. The test build is still Java 6 and
>>>> that
>>>> usually works; it might be load-on-build-server sensitive. It builds
>>>> fully on my local machine in either set up. (I have added connection
>>>> caching to Fuseki test as well.)
>>>>
>>>>> What are the build exceptions in JDBC / JenaStatement?
>>>>
>>>> There's log at:
>>>>
>>>> https://builds.apache.org/job/Jena_Development_Deploy/437/console
>>>>
>>> >from about 25% to 50% of the scroll bar.
>>>>
>>>> I have a version locally that is clean. I found that the tests reset
>>>> Log4j and then remove all the appenders which causes the warning about
>>>>
>>>> log4j:WARN No appenders could be found for logger
>>>> (org.apache.jena.riot.stream.JenaIOEnvironment).
>>>> etc
>>>>
>>>> but it also stops configuring the logging from src/test/resources as
>>>> this is ignored. That confused me for a while :-)
>>>>
>>>> I'd guess this was just debugging setup? Also, there is logging to a
>>>> file, I switched that off as well.
>>>
>>> This was kind of intentional, when I was debugging in isolation prior to
>>> having Jena as a parent I guess the src/test/resources was never
>>> applicable
>>
>> Shall I commit my changes? They switch logging off in the tests for the
>> things that are expected to log. The exceptions are printed log
>> messages so they don't them appear - it's not clear looking at the build
>> job console output that is the case and that they are not real unhandled
>> exceptions.
>>
>> (/me still unclear as to why it removes all the appenders)
>>
>>>
>>>>
>>>> jena-jdbc-log4j.properties, which is src/main so goes in the final jar
>>>> but as far as I can see, it's only used in TestMemDriverWithLogging.
>>>
>>> This was primarily intended as an example for users, it does also get
>>> used
>>> to test that the JDBC connection parameter for logging works correctly
>>> in
>>> that test class as noted.
>>
>> So leave it in src/main/resources?
>>
>> How would the user find it?
>>
>>>
>>>>
>>>> A question:
>>>>
>>>> The POM says aspectj plugin is for debugging purposes.
>>>>
>>>> (and how do you get it working with Eclipse? When I add a maven nature
>>>> I get errors and Eclipse refuses to compile the JDBC projects).
>>>
>>> There is an AspectJ Development Tools (AJDT) that you can install which
>>> provides AspectJ support within Eclipse. AspectJ is used to add method
>>> entry and exit trace logging which is very useful when trying the
>>> drivers
>>> with a new tool to see where (if anywhere) things break.
>>
>> Thanks for that.
>>
>> Andy
>>
>>>
>>> Rob
>>>
>>>>
>>>> Andy
>>>>
>>>>
>>>
>>
>
Re: Build and prep for 2.11.0
Posted by Rob Vesse <rv...@yarcdata.com>.
They remove all appenders because things other than JDBC may have caused
the loggers to be set up some way and doing
BasicConfigurer.configure()/BasicConfigurer.resetConfiguration() ends up
setting up a single console appender.
If you have a better way of disabling logging for the tests then that
would be preferred. Also the one TestMemDriverWithLogging class
explicitly wants to configure logging because it is changing the logging
setup at driver creation time to verify that portion of functionality.
Currently this is redirecting stdout to a ByteArrayOutputStream so as to
not pollute the build output.
I likely need to add a note to the documentation about example logging
configuration being available.
I'm away on vacation through Wednesday so don't expect any responses from
me in the meantime I.e. don't let me hold you up if you want/need to make
changes to get the release prepared.
Rob
On 9/8/13 2:20 AM, "Andy Seaborne" <an...@apache.org> wrote:
>On 07/09/13 21:55, Rob Vesse wrote:
>> Comments inline:
>>
>>
>> On 9/7/13 12:50 PM, "Andy Seaborne" <an...@apache.org> wrote:
>>
>>> Hi Rob,
>>>
>>> I've got the full build (deploy) building by using java7. It's not
>>>that
>>> it is always broken with Java6. The test build is still Java 6 and
>>>that
>>> usually works; it might be load-on-build-server sensitive. It builds
>>> fully on my local machine in either set up. (I have added connection
>>> caching to Fuseki test as well.)
>>>
>>>> What are the build exceptions in JDBC / JenaStatement?
>>>
>>> There's log at:
>>>
>>> https://builds.apache.org/job/Jena_Development_Deploy/437/console
>>>
>>>from about 25% to 50% of the scroll bar.
>>>
>>> I have a version locally that is clean. I found that the tests reset
>>> Log4j and then remove all the appenders which causes the warning about
>>>
>>> log4j:WARN No appenders could be found for logger
>>> (org.apache.jena.riot.stream.JenaIOEnvironment).
>>> etc
>>>
>>> but it also stops configuring the logging from src/test/resources as
>>> this is ignored. That confused me for a while :-)
>>>
>>> I'd guess this was just debugging setup? Also, there is logging to a
>>> file, I switched that off as well.
>>
>> This was kind of intentional, when I was debugging in isolation prior to
>> having Jena as a parent I guess the src/test/resources was never
>>applicable
>
>Shall I commit my changes? They switch logging off in the tests for the
>things that are expected to log. The exceptions are printed log
>messages so they don't them appear - it's not clear looking at the build
>job console output that is the case and that they are not real unhandled
>exceptions.
>
>(/me still unclear as to why it removes all the appenders)
>
>>
>>>
>>> jena-jdbc-log4j.properties, which is src/main so goes in the final jar
>>> but as far as I can see, it's only used in TestMemDriverWithLogging.
>>
>> This was primarily intended as an example for users, it does also get
>>used
>> to test that the JDBC connection parameter for logging works correctly
>>in
>> that test class as noted.
>
>So leave it in src/main/resources?
>
>How would the user find it?
>
>>
>>>
>>> A question:
>>>
>>> The POM says aspectj plugin is for debugging purposes.
>>>
>>> (and how do you get it working with Eclipse? When I add a maven nature
>>> I get errors and Eclipse refuses to compile the JDBC projects).
>>
>> There is an AspectJ Development Tools (AJDT) that you can install which
>> provides AspectJ support within Eclipse. AspectJ is used to add method
>> entry and exit trace logging which is very useful when trying the
>>drivers
>> with a new tool to see where (if anywhere) things break.
>
>Thanks for that.
>
> Andy
>
>>
>> Rob
>>
>>>
>>> Andy
>>>
>>>
>>
>
Re: Build and prep for 2.11.0
Posted by Andy Seaborne <an...@apache.org>.
On 07/09/13 21:55, Rob Vesse wrote:
> Comments inline:
>
>
> On 9/7/13 12:50 PM, "Andy Seaborne" <an...@apache.org> wrote:
>
>> Hi Rob,
>>
>> I've got the full build (deploy) building by using java7. It's not that
>> it is always broken with Java6. The test build is still Java 6 and that
>> usually works; it might be load-on-build-server sensitive. It builds
>> fully on my local machine in either set up. (I have added connection
>> caching to Fuseki test as well.)
>>
>>> What are the build exceptions in JDBC / JenaStatement?
>>
>> There's log at:
>>
>> https://builds.apache.org/job/Jena_Development_Deploy/437/console
>>
>>from about 25% to 50% of the scroll bar.
>>
>> I have a version locally that is clean. I found that the tests reset
>> Log4j and then remove all the appenders which causes the warning about
>>
>> log4j:WARN No appenders could be found for logger
>> (org.apache.jena.riot.stream.JenaIOEnvironment).
>> etc
>>
>> but it also stops configuring the logging from src/test/resources as
>> this is ignored. That confused me for a while :-)
>>
>> I'd guess this was just debugging setup? Also, there is logging to a
>> file, I switched that off as well.
>
> This was kind of intentional, when I was debugging in isolation prior to
> having Jena as a parent I guess the src/test/resources was never applicable
Shall I commit my changes? They switch logging off in the tests for the
things that are expected to log. The exceptions are printed log
messages so they don't them appear - it's not clear looking at the build
job console output that is the case and that they are not real unhandled
exceptions.
(/me still unclear as to why it removes all the appenders)
>
>>
>> jena-jdbc-log4j.properties, which is src/main so goes in the final jar
>> but as far as I can see, it's only used in TestMemDriverWithLogging.
>
> This was primarily intended as an example for users, it does also get used
> to test that the JDBC connection parameter for logging works correctly in
> that test class as noted.
So leave it in src/main/resources?
How would the user find it?
>
>>
>> A question:
>>
>> The POM says aspectj plugin is for debugging purposes.
>>
>> (and how do you get it working with Eclipse? When I add a maven nature
>> I get errors and Eclipse refuses to compile the JDBC projects).
>
> There is an AspectJ Development Tools (AJDT) that you can install which
> provides AspectJ support within Eclipse. AspectJ is used to add method
> entry and exit trace logging which is very useful when trying the drivers
> with a new tool to see where (if anywhere) things break.
Thanks for that.
Andy
>
> Rob
>
>>
>> Andy
>>
>>
>
Re: Build and prep for 2.11.0
Posted by Rob Vesse <rv...@yarcdata.com>.
Comments inline:
On 9/7/13 12:50 PM, "Andy Seaborne" <an...@apache.org> wrote:
>Hi Rob,
>
>I've got the full build (deploy) building by using java7. It's not that
>it is always broken with Java6. The test build is still Java 6 and that
>usually works; it might be load-on-build-server sensitive. It builds
>fully on my local machine in either set up. (I have added connection
>caching to Fuseki test as well.)
>
> > What are the build exceptions in JDBC / JenaStatement?
>
>There's log at:
>
>https://builds.apache.org/job/Jena_Development_Deploy/437/console
>
>from about 25% to 50% of the scroll bar.
>
>I have a version locally that is clean. I found that the tests reset
>Log4j and then remove all the appenders which causes the warning about
>
>log4j:WARN No appenders could be found for logger
>(org.apache.jena.riot.stream.JenaIOEnvironment).
>etc
>
>but it also stops configuring the logging from src/test/resources as
>this is ignored. That confused me for a while :-)
>
>I'd guess this was just debugging setup? Also, there is logging to a
>file, I switched that off as well.
This was kind of intentional, when I was debugging in isolation prior to
having Jena as a parent I guess the src/test/resources was never applicable
>
>jena-jdbc-log4j.properties, which is src/main so goes in the final jar
>but as far as I can see, it's only used in TestMemDriverWithLogging.
This was primarily intended as an example for users, it does also get used
to test that the JDBC connection parameter for logging works correctly in
that test class as noted.
>
>A question:
>
>The POM says aspectj plugin is for debugging purposes.
>
>(and how do you get it working with Eclipse? When I add a maven nature
>I get errors and Eclipse refuses to compile the JDBC projects).
There is an AspectJ Development Tools (AJDT) that you can install which
provides AspectJ support within Eclipse. AspectJ is used to add method
entry and exit trace logging which is very useful when trying the drivers
with a new tool to see where (if anywhere) things break.
Rob
>
> Andy
>
>
Re: Build and prep for 2.11.0
Posted by Andy Seaborne <an...@apache.org>.
Hi Rob,
I've got the full build (deploy) building by using java7. It's not that
it is always broken with Java6. The test build is still Java 6 and that
usually works; it might be load-on-build-server sensitive. It builds
fully on my local machine in either set up. (I have added connection
caching to Fuseki test as well.)
> What are the build exceptions in JDBC / JenaStatement?
There's log at:
https://builds.apache.org/job/Jena_Development_Deploy/437/console
from about 25% to 50% of the scroll bar.
I have a version locally that is clean. I found that the tests reset
Log4j and then remove all the appenders which causes the warning about
log4j:WARN No appenders could be found for logger
(org.apache.jena.riot.stream.JenaIOEnvironment).
etc
but it also stops configuring the logging from src/test/resources as
this is ignored. That confused me for a while :-)
I'd guess this was just debugging setup? Also, there is logging to a
file, I switched that off as well.
jena-jdbc-log4j.properties, which is src/main so goes in the final jar
but as far as I can see, it's only used in TestMemDriverWithLogging.
A question:
The POM says aspectj plugin is for debugging purposes.
(and how do you get it working with Eclipse? When I add a maven nature
I get errors and Eclipse refuses to compile the JDBC projects).
Andy
Re: Build and prep for 2.11.0
Posted by Rob Vesse <rv...@yarcdata.com>.
What are the build exceptions in JDBC / JenaStatement?
Rob
On 9/6/13 2:29 PM, "Andy Seaborne" <an...@apache.org> wrote:
>Is everything ready?
>
>All the modules are now integrated into the build and the snapshots will
> now be what the release is except for signing and version numbers so
>please poke and prod the builds.
>
>I've made some changes:
>
>1/ Instead of the default being a developer build, the default is a
>complete build and there is a restricted set of modules built with
>profile "dev". This is to avoid mistakes doing a release :-)
>
>The Jenkins deploy job is now doing a full build (which takes 15mins on
>my machine even without any uploads).
>
>The Jenkins test job is a -Pdev build.
>
>Maybe we need more profiles. Please take a look and see what
>improvements can be made.
>
>2/ jena-spatial now in the Fuseki server build
>
>Still need to check the distribution versions of NOTICE and LICENSE but
>jena-spatial only adds com.spatial4j:spatial4j over what that added by
>jena-text.
>
>3/ Include SDB in apache-jena
>
>jena-sdb in the apache-jena lib/ directory.
>
>Not sure is this is the right thing to do - opinions? options?
>
>4/ The website needs link checking
>
>Could someone volunteer and run a link checker on the staging site? I
>think some of converted pages may have bad internal links - this is
>probably not new.
>
>5/ The build exceptions in JDBC / JenaStatement
>
>... are really quite worrying to the RM!
>
>6/ An "advanced notice" email sent to users@
>
> Andy