You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Onder SEZGIN <on...@gmail.com> on 2017/06/06 05:10:21 UTC

Re: checkstyle plugin problem

Hi,

I am building on my local.
and if i build buildingtools and after try to run

- mvn clean install -Psourcecheck

I get lots of checkstyle errors.

However, if i go to my local repo and delete camel-buildtools folder and
afterwards if i run the build for the same component.
Checkstyle seems fine.

so i found out after comparing both the jar file downloaded by maven and my
locally built camel-buildtools-2.20.0-SNAPSHOT jar files, that

<module name="Header"> part has small difference due to new lines (which is
in my local build whereas the one on apache repos has single line. )

The source code on my local has single line for them too, i am not sure how
they become multi line and causes failure.

Any clue appreciated.

Thanks.



On Wed, May 17, 2017 at 10:52 AM, Zoran Regvart <zo...@regvart.com> wrote:

> Hi Önder,
> yeah, snapshots are at repository.apache.org[1] perhaps you can get
> that Archiva instance to proxy[2] to:
>
> https://repository.apache.org/content/groups/public/
>
> zoran
>
> [1] https://repository.apache.org/#nexus-search;gav~org.apache.
> camel~camel-core~2.20.0-SNAPSHOT~~
> [2] https://archiva.apache.org/docs/2.2.3/adminguide/proxy-connectors.html
>
> On Wed, May 17, 2017 at 9:43 AM, Onder SEZGIN <on...@gmail.com>
> wrote:
> > Hi Zoran,
> >
> > apparently we have archiava running which has not been maintained for a
> > long time.
> >
> > i figured out that archiava has access to maven public repo. so i changed
> > my maven's setting.xml to point that archiava. however i am failing to
> run
> > mvn install. i guess it does not have access to snapshot repos. i'll try
> to
> > check and see. thanks for your advices.
> >
> > Önder
> >
> >
> > On Tue, 16 May 2017 at 09:13, Zoran Regvart <zo...@regvart.com> wrote:
> >
> >> Hi Önder,
> >> that's a real bummer :(
> >>
> >> Perhaps you you can make the case that it's needed for work and it
> >> ruins everybody's productivity and convince the IT to either pass
> >> certain sites (like repo.maven.org and repository.apache.org), or can
> >> run a Maven repository manager (like Nexus) and the IT can allow the
> >> that host to access the internet without proxy.
> >>
> >> zoran
> >>
> >> On Mon, May 15, 2017 at 9:14 PM, Onder SEZGIN <on...@gmail.com>
> >> wrote:
> >> > well, obviously
> >> > i've tried different settings today but have not come up with a
> result.
> >> >
> >> > Unless network admin does change the policy, i don't seem to connect.
> >> > For reference i would like share wget result. (in my previous post,
> i'd
> >> > mentioned i could use wget. this is partially connect. i can get jar
> file
> >> > maven http repos but for snapshots i guess the situation is a bit
> >> different
> >> > event http and https results in the same telling that 302-HTTP status)
> >> >
> >> >
> >> > $ wget -e http_proxy=http://127.0.0.1:3128 --no-check-certificate
> >> >
> >> http://repository.apache.org/content/groups/snapshots/org/
> apache/camel/camel-buildtools/2.20.0-SNAPSHOT/camel-
> buildtools-2.20.0-20170511.100836-14.jar
> >> >
> >> > --2017-05-15 21:59:57--
> >> >
> >> http://repository.apache.org/content/groups/snapshots/org/
> apache/camel/camel-buildtools/2.20.0-SNAPSHOT/camel-
> buildtools-2.20.0-20170511.100836-14.jar
> >> > Connecting to 127.0.0.1:3128... connected.
> >> > Proxy request sent, awaiting response... 302 Moved Temporarily
> >> > Location: http://
> >> <corporate_ip>:<corporate_port>/cgi-bin/blockpage.cgi?
> ws-session=929304523
> >> > [following]
> >> > --2017-05-15 22:00:39--  http://
> >> >
> >> <corporate_ip>:<corporate_port>/cgi-bin/blockpage.cgi?
> ws-session=929304523
> >> > Connecting to 127.0.0.1:3128... connected.
> >> > Proxy request sent, awaiting response... 200 OK
> >> > Length: 1990 (1.9K) [text/html]
> >> > Saving to: ‘camel-buildtools-2.20.0-20170511.100836-14.jar.3’
> >> >
> >> > camel-buildtools-2.20.0-20170511.100836-14.jar.3
> >> >
> >> 100%[=======================================================
> ========================================================================>]
> >> >   1.94K  --.-KB/s    in 0s
> >> >
> >> > 2017-05-15 22:00:39 (55.7 MB/s) -
> >> > ‘camel-buildtools-2.20.0-20170511.100836-14.jar.3’ saved [1990/1990]
> >>
> >>
> >>
> >> --
> >> Zoran Regvart
> >>
> > --
> > Sent from my iPhone
>
>
>
> --
> Zoran Regvart
>

Re: checkstyle plugin problem

Posted by Onder SEZGIN <on...@gmail.com>.
Thanks Zoran. You seem to provide it. I have tested on Windows(yes it was
windows), it is working.
Thanks

On Tue, Jun 6, 2017 at 4:57 PM, Zoran Regvart <zo...@regvart.com> wrote:

> Hi Önder,
> there is a small beanshell script that converts the header-*.txt files
> into string expressions expected by checkstyle[1].
> It somewhat strange process but the idea is that there is only one
> header.txt[2] and all other header-*.txt files are generated from it.
> My guess is that I haven't thought about platform line endings in that
> beanshell script, and when you build on your machine (Windows?) it
> fails to produce the same as on Unix,
>
> I'll take a look it should be a simple fix,
>
> zoran
>
> [1] https://github.com/apache/camel/blob/master/
> buildingtools/pom.xml#L106-L111
> [2] https://github.com/apache/camel/blob/master/buildingtools/src/main/
> resources/header.txt
>
> On Tue, Jun 6, 2017 at 7:10 AM, Onder SEZGIN <on...@gmail.com>
> wrote:
> > Hi,
> >
> > I am building on my local.
> > and if i build buildingtools and after try to run
> >
> > - mvn clean install -Psourcecheck
> >
> > I get lots of checkstyle errors.
> >
> > However, if i go to my local repo and delete camel-buildtools folder and
> > afterwards if i run the build for the same component.
> > Checkstyle seems fine.
> >
> > so i found out after comparing both the jar file downloaded by maven and
> my
> > locally built camel-buildtools-2.20.0-SNAPSHOT jar files, that
> >
> > <module name="Header"> part has small difference due to new lines (which
> is
> > in my local build whereas the one on apache repos has single line. )
> >
> > The source code on my local has single line for them too, i am not sure
> how
> > they become multi line and causes failure.
> >
> > Any clue appreciated.
> >
> > Thanks.
> >
> >
> >
> > On Wed, May 17, 2017 at 10:52 AM, Zoran Regvart <zo...@regvart.com>
> wrote:
> >
> >> Hi Önder,
> >> yeah, snapshots are at repository.apache.org[1] perhaps you can get
> >> that Archiva instance to proxy[2] to:
> >>
> >> https://repository.apache.org/content/groups/public/
> >>
> >> zoran
> >>
> >> [1] https://repository.apache.org/#nexus-search;gav~org.apache.
> >> camel~camel-core~2.20.0-SNAPSHOT~~
> >> [2] https://archiva.apache.org/docs/2.2.3/adminguide/proxy-
> connectors.html
> >>
> >> On Wed, May 17, 2017 at 9:43 AM, Onder SEZGIN <on...@gmail.com>
> >> wrote:
> >> > Hi Zoran,
> >> >
> >> > apparently we have archiava running which has not been maintained for
> a
> >> > long time.
> >> >
> >> > i figured out that archiava has access to maven public repo. so i
> changed
> >> > my maven's setting.xml to point that archiava. however i am failing to
> >> run
> >> > mvn install. i guess it does not have access to snapshot repos. i'll
> try
> >> to
> >> > check and see. thanks for your advices.
> >> >
> >> > Önder
> >> >
> >> >
> >> > On Tue, 16 May 2017 at 09:13, Zoran Regvart <zo...@regvart.com>
> wrote:
> >> >
> >> >> Hi Önder,
> >> >> that's a real bummer :(
> >> >>
> >> >> Perhaps you you can make the case that it's needed for work and it
> >> >> ruins everybody's productivity and convince the IT to either pass
> >> >> certain sites (like repo.maven.org and repository.apache.org), or
> can
> >> >> run a Maven repository manager (like Nexus) and the IT can allow the
> >> >> that host to access the internet without proxy.
> >> >>
> >> >> zoran
> >> >>
> >> >> On Mon, May 15, 2017 at 9:14 PM, Onder SEZGIN <ondersezgin@gmail.com
> >
> >> >> wrote:
> >> >> > well, obviously
> >> >> > i've tried different settings today but have not come up with a
> >> result.
> >> >> >
> >> >> > Unless network admin does change the policy, i don't seem to
> connect.
> >> >> > For reference i would like share wget result. (in my previous post,
> >> i'd
> >> >> > mentioned i could use wget. this is partially connect. i can get
> jar
> >> file
> >> >> > maven http repos but for snapshots i guess the situation is a bit
> >> >> different
> >> >> > event http and https results in the same telling that 302-HTTP
> status)
> >> >> >
> >> >> >
> >> >> > $ wget -e http_proxy=http://127.0.0.1:3128 --no-check-certificate
> >> >> >
> >> >> http://repository.apache.org/content/groups/snapshots/org/
> >> apache/camel/camel-buildtools/2.20.0-SNAPSHOT/camel-
> >> buildtools-2.20.0-20170511.100836-14.jar
> >> >> >
> >> >> > --2017-05-15 21:59:57--
> >> >> >
> >> >> http://repository.apache.org/content/groups/snapshots/org/
> >> apache/camel/camel-buildtools/2.20.0-SNAPSHOT/camel-
> >> buildtools-2.20.0-20170511.100836-14.jar
> >> >> > Connecting to 127.0.0.1:3128... connected.
> >> >> > Proxy request sent, awaiting response... 302 Moved Temporarily
> >> >> > Location: http://
> >> >> <corporate_ip>:<corporate_port>/cgi-bin/blockpage.cgi?
> >> ws-session=929304523
> >> >> > [following]
> >> >> > --2017-05-15 22:00:39--  http://
> >> >> >
> >> >> <corporate_ip>:<corporate_port>/cgi-bin/blockpage.cgi?
> >> ws-session=929304523
> >> >> > Connecting to 127.0.0.1:3128... connected.
> >> >> > Proxy request sent, awaiting response... 200 OK
> >> >> > Length: 1990 (1.9K) [text/html]
> >> >> > Saving to: ‘camel-buildtools-2.20.0-20170511.100836-14.jar.3’
> >> >> >
> >> >> > camel-buildtools-2.20.0-20170511.100836-14.jar.3
> >> >> >
> >> >> 100%[=======================================================
> >> ============================================================
> ============>]
> >> >> >   1.94K  --.-KB/s    in 0s
> >> >> >
> >> >> > 2017-05-15 22:00:39 (55.7 MB/s) -
> >> >> > ‘camel-buildtools-2.20.0-20170511.100836-14.jar.3’ saved
> [1990/1990]
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Zoran Regvart
> >> >>
> >> > --
> >> > Sent from my iPhone
> >>
> >>
> >>
> >> --
> >> Zoran Regvart
> >>
>
>
>
> --
> Zoran Regvart
>

Re: checkstyle plugin problem

Posted by Zoran Regvart <zo...@regvart.com>.
Hi Önder,
there is a small beanshell script that converts the header-*.txt files
into string expressions expected by checkstyle[1].
It somewhat strange process but the idea is that there is only one
header.txt[2] and all other header-*.txt files are generated from it.
My guess is that I haven't thought about platform line endings in that
beanshell script, and when you build on your machine (Windows?) it
fails to produce the same as on Unix,

I'll take a look it should be a simple fix,

zoran

[1] https://github.com/apache/camel/blob/master/buildingtools/pom.xml#L106-L111
[2] https://github.com/apache/camel/blob/master/buildingtools/src/main/resources/header.txt

On Tue, Jun 6, 2017 at 7:10 AM, Onder SEZGIN <on...@gmail.com> wrote:
> Hi,
>
> I am building on my local.
> and if i build buildingtools and after try to run
>
> - mvn clean install -Psourcecheck
>
> I get lots of checkstyle errors.
>
> However, if i go to my local repo and delete camel-buildtools folder and
> afterwards if i run the build for the same component.
> Checkstyle seems fine.
>
> so i found out after comparing both the jar file downloaded by maven and my
> locally built camel-buildtools-2.20.0-SNAPSHOT jar files, that
>
> <module name="Header"> part has small difference due to new lines (which is
> in my local build whereas the one on apache repos has single line. )
>
> The source code on my local has single line for them too, i am not sure how
> they become multi line and causes failure.
>
> Any clue appreciated.
>
> Thanks.
>
>
>
> On Wed, May 17, 2017 at 10:52 AM, Zoran Regvart <zo...@regvart.com> wrote:
>
>> Hi Önder,
>> yeah, snapshots are at repository.apache.org[1] perhaps you can get
>> that Archiva instance to proxy[2] to:
>>
>> https://repository.apache.org/content/groups/public/
>>
>> zoran
>>
>> [1] https://repository.apache.org/#nexus-search;gav~org.apache.
>> camel~camel-core~2.20.0-SNAPSHOT~~
>> [2] https://archiva.apache.org/docs/2.2.3/adminguide/proxy-connectors.html
>>
>> On Wed, May 17, 2017 at 9:43 AM, Onder SEZGIN <on...@gmail.com>
>> wrote:
>> > Hi Zoran,
>> >
>> > apparently we have archiava running which has not been maintained for a
>> > long time.
>> >
>> > i figured out that archiava has access to maven public repo. so i changed
>> > my maven's setting.xml to point that archiava. however i am failing to
>> run
>> > mvn install. i guess it does not have access to snapshot repos. i'll try
>> to
>> > check and see. thanks for your advices.
>> >
>> > Önder
>> >
>> >
>> > On Tue, 16 May 2017 at 09:13, Zoran Regvart <zo...@regvart.com> wrote:
>> >
>> >> Hi Önder,
>> >> that's a real bummer :(
>> >>
>> >> Perhaps you you can make the case that it's needed for work and it
>> >> ruins everybody's productivity and convince the IT to either pass
>> >> certain sites (like repo.maven.org and repository.apache.org), or can
>> >> run a Maven repository manager (like Nexus) and the IT can allow the
>> >> that host to access the internet without proxy.
>> >>
>> >> zoran
>> >>
>> >> On Mon, May 15, 2017 at 9:14 PM, Onder SEZGIN <on...@gmail.com>
>> >> wrote:
>> >> > well, obviously
>> >> > i've tried different settings today but have not come up with a
>> result.
>> >> >
>> >> > Unless network admin does change the policy, i don't seem to connect.
>> >> > For reference i would like share wget result. (in my previous post,
>> i'd
>> >> > mentioned i could use wget. this is partially connect. i can get jar
>> file
>> >> > maven http repos but for snapshots i guess the situation is a bit
>> >> different
>> >> > event http and https results in the same telling that 302-HTTP status)
>> >> >
>> >> >
>> >> > $ wget -e http_proxy=http://127.0.0.1:3128 --no-check-certificate
>> >> >
>> >> http://repository.apache.org/content/groups/snapshots/org/
>> apache/camel/camel-buildtools/2.20.0-SNAPSHOT/camel-
>> buildtools-2.20.0-20170511.100836-14.jar
>> >> >
>> >> > --2017-05-15 21:59:57--
>> >> >
>> >> http://repository.apache.org/content/groups/snapshots/org/
>> apache/camel/camel-buildtools/2.20.0-SNAPSHOT/camel-
>> buildtools-2.20.0-20170511.100836-14.jar
>> >> > Connecting to 127.0.0.1:3128... connected.
>> >> > Proxy request sent, awaiting response... 302 Moved Temporarily
>> >> > Location: http://
>> >> <corporate_ip>:<corporate_port>/cgi-bin/blockpage.cgi?
>> ws-session=929304523
>> >> > [following]
>> >> > --2017-05-15 22:00:39--  http://
>> >> >
>> >> <corporate_ip>:<corporate_port>/cgi-bin/blockpage.cgi?
>> ws-session=929304523
>> >> > Connecting to 127.0.0.1:3128... connected.
>> >> > Proxy request sent, awaiting response... 200 OK
>> >> > Length: 1990 (1.9K) [text/html]
>> >> > Saving to: ‘camel-buildtools-2.20.0-20170511.100836-14.jar.3’
>> >> >
>> >> > camel-buildtools-2.20.0-20170511.100836-14.jar.3
>> >> >
>> >> 100%[=======================================================
>> ========================================================================>]
>> >> >   1.94K  --.-KB/s    in 0s
>> >> >
>> >> > 2017-05-15 22:00:39 (55.7 MB/s) -
>> >> > ‘camel-buildtools-2.20.0-20170511.100836-14.jar.3’ saved [1990/1990]
>> >>
>> >>
>> >>
>> >> --
>> >> Zoran Regvart
>> >>
>> > --
>> > Sent from my iPhone
>>
>>
>>
>> --
>> Zoran Regvart
>>



-- 
Zoran Regvart