[
https://issues.apache.org/jira/browse/JENA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302657#comment-14302657
]
Stian Soiland-Reyes commented on JENA-879:
--
An alternative using the PAX solution i
Ouch.. seems like a bug in Maven (or more likely) this magic
org.rzo.yajsw.os.posix.PosixProcess used by org.everit.osgi.
I guess setting it manually with -Djna.nosys=true didn't help either?
Another reason to have a quick look at the PAX Exam (JENA-879) - which
I'm in the middle of now. It's mu
Thanks Andy
That sounds like a sensible compromise to me
Rob
On 01/02/2015 11:29, "Andy Seaborne" wrote:
>> On 26/01/15 19:11, Rob Vesse wrote:
>> Could people please review the following JIRA filter:
>>>
>>> http://s.apache.org/jena-no-fix-version
>>>
>>>
>>> This lists all resolved Jena issu
On 02/02/15 11:33, Stian Soiland-Reyes wrote:
1/ Build failure
>
>jena-osgi-test fails the build in step "verify"
>
>tried: java-8-openjdk and java-7-openjdk
>
>
>Exception in thread "main" java.lang.Error:
>
>There is an incompatible JNA native library installed on this s
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/5
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
On 02/02/15 17:45, stain wrote:
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/24
Apache jena osgi
Builds on #21 by splitting out jena-osgi* to submodules under
`apache-jena-osgi`.
Merges in #21, #22, #23
Combined pull requests are harder t
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/23
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/21
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
On 02/02/15 17:50, Stian Soiland-Reyes wrote:
OK, agree that it should be easy out of the box to compile.
With remove you mean to move out of source code or just not include it
in the release?
Out of the source tree. That's clear cut.
Just disabling it in (or require the -Papache-release f
On 2 February 2015 at 17:03, Andy Seaborne wrote:
> I think it's a different audience.
>
> apache-jena-dist is for standalong use + source + javadoc.
Right, that is what I would prefer as well.
So if/when we go for a Jena-OSGi download, it would be a separate one.
So you are happy with its bina
OK, agree that it should be easy out of the box to compile.
With remove you mean to move out of source code or just not include it
in the release?
Just disabling it in (or require the -Papache-release flag)
would work for me.
The test source is IP and license clean - so there's no issue with it
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/24
Apache jena osgi
Builds on #21 by splitting out jena-osgi* to submodules under
`apache-jena-osgi`.
Merges in #21, #22, #23
You can merge this pull request into a Git repository by running:
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/23
rat: exlude anything under target/*
.. as it only excluded `target/.plxarc`
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena parent-rat-excl
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/22
NOTICE file for jena-osgi
stripped version of apache-jena/NOTICE
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena jena-osgi-NOTICE
Alternat
[
https://issues.apache.org/jira/browse/JENA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301473#comment-14301473
]
Andy Seaborne commented on JENA-879:
The impliciation of "thin line" seems to be that th
[
https://issues.apache.org/jira/browse/JENA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-879:
---
Issue Type: Improvement (was: Task)
> Use PAX Exam for jena-osgi-test
> ---
[
https://issues.apache.org/jira/browse/JENA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-879:
---
Issue Type: Task (was: Improvement)
> Use PAX Exam for jena-osgi-test
> ---
[
https://issues.apache.org/jira/browse/JENA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-879:
---
Priority: Major (was: Minor)
> Use PAX Exam for jena-osgi-test
> ---
>
>
On 02/02/15 11:53, Stian Soiland-Reyes wrote:
Did you mean to just include the jena-osgi.jar in the apache-jena/
dist? It would add only 7 MB.
I think it's a different audience.
apache-jena-dist is for standalong use + source + javadoc.
I'd rather start cautious and add later, rather than add
I don't see this in the mailing list archive.
> Also included the NOTICE to include the historical Jena NOTICEs and
Xerces.
Please can we keep things like fixing comments and fixing the build
separate from setting NOTICE.
I'd like to be able to pull whole requests, not pick up some commits
[
https://issues.apache.org/jira/browse/JENA-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301237#comment-14301237
]
Andy Seaborne edited comment on JENA-878 at 2/2/15 3:38 PM:
Jena
On 02/02/15 13:30, Stian Soiland-Reyes wrote:
So the jena-osgi-test is not needed for *building* any artifacts
(except itself, which doesn't depend on LGPL but probably need not be
pushed to Maven central anyway). jena-osgi-test is not required for
anything else. The test is only run during the i
On 02/02/15 14:11, Stian Soiland-Reyes wrote:
Tracked as:
https://issues.apache.org/jira/browse/JENA-879
(I'm unable to assign it to myself in Jira - anyone else want to have a go?:-)
There are two roles here - the committer who lets it into the code base
the doer who makes the contribution.
[
https://issues.apache.org/jira/browse/JENA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reassigned JENA-879:
--
Assignee: Andy Seaborne
> Use PAX Exam for jena-osgi-test
> ---
>
>
[
https://issues.apache.org/jira/browse/JENA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-879:
---
Assignee: (was: Andy Seaborne)
> Use PAX Exam for jena-osgi-test
> ---
>
Side-note - https://builds.apache.org/view/All/job/Jena_Development_Test/
doesn't have any special profiles it activates, so as it stands with
my new pull request, jena-osgi-test would not be tested by Jenkins.
(Perhaps activation by either -Papache-release or -Pall-tests ? )
On 2 February 2015
Thanks for the hint, Benson! I had looked at PAX before without
figuring it out, but this time I found more documentation, and it
looks like it is definitely worth a try (even if it has a bit more
heavyweight setup than eosgi).
Tracked as:
https://issues.apache.org/jira/browse/JENA-879
(I'm unabl
Stian Soiland-Reyes created JENA-879:
Summary: Use PAX Exam for jena-osgi-test
Key: JENA-879
URL: https://issues.apache.org/jira/browse/JENA-879
Project: Apache Jena
Issue Type: Task
On 2 February 2015 at 13:11, Andy Seaborne wrote:
> As far as I know, we can not ship source-release that pulls in LGPL, even to
> test, without the user making an explicit act to knowingly do that and work
> without it.
Some relevant LEGAL issues (which don't really clarify as they ask for
the
So the jena-osgi-test is not needed for *building* any artifacts
(except itself, which doesn't depend on LGPL but probably need not be
pushed to Maven central anyway). jena-osgi-test is not required for
anything else. The test is only run during the integration-test phase
(which happens during mvn
The maven-bundle-plugin + the pax-exam tools make for a full AL
solution to making bundles and testing bundles.
See, for example:
https://github.com/basis-technology-corp/tcl-regex-java
On Mon, Feb 2, 2015 at 8:11 AM, Andy Seaborne wrote:
> On 02/02/15 11:33, Stian Soiland-Reyes wrote:
>>>
>>>
On 02/02/15 11:33, Stian Soiland-Reyes wrote:
2/ There is a LGPL dependency (scope test) which needs investigation.
>(I would have appreciated that having been pointed out first)
Sorry, I didn't mention this outside the pom.xml as it was a
build/test dependency, which I thought would be OK - giv
[
https://issues.apache.org/jira/browse/JENA-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301237#comment-14301237
]
Andy Seaborne commented on JENA-878:
Jena uses Xerces vd and below in the datatype code
As do I!
I added to the pull request
true
to both according to
http://www.everit.org/eosgi-maven-plugin/#environment_settings
Could you test if it works now?
On 2 February 2015 at 11:46, Andy Seaborne wrote:
> On 02/02/15 11:3
Did you mean to just include the jena-osgi.jar in the apache-jena/
dist? It would add only 7 MB.
If on the otherside we do a separate download of jena-osgi, we
probably want a separate 'apache-' like dist ZIP/tar.gz instead of the
direct JAR file - not sure how well the mirrors (and anti virus
s
On 02/02/15 11:33, Stian Soiland-Reyes wrote:
I'm not sure what JNl library you have, possibly some OS X thing?
I'm on Ubuntu 14.10
Andy
On 1 February 2015 at 13:12, Andy Seaborne wrote:
> Current status:
>
> * Pull request merged
Thanks!
> * jena-osgi-test commented out of the build
>* Fatal problem building
>* LGPL issue (not an issue ATM as not in the build)
Oh no :-(
> 1/ Build failure
>
> jena-osgi-test fails the b
Stian Soiland-Reyes created JENA-878:
Summary: Avoid dependencies on xerces.impl
Key: JENA-878
URL: https://issues.apache.org/jira/browse/JENA-878
Project: Apache Jena
Issue Type: Task
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/21
Remove outdated jsonld comments
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena jena-osgi-tidy
Alternatively you can review and apply the
39 matches
Mail list logo
